metadata between vms

[adica...@gmail.com]

Can someone answer or point to me a place in the docs for this.
I want to know about the level of metadata sharing between the writing OS, the disk, aswell as between new vms and the OS itself.
When i dd my verified OS to my usb i assume some amount of identifiable info is on the disk.
This isnt neccesarily about attack risk, more about anonymity.

[adica...@gmail.com]

Writing OS being where i dd from my old, potentially at risk OS

[Andrew David Wong]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 2016-08-15 02:31, adica...@gmail.com wrote:
> Writing OS being where i dd from my old, potentially at risk OS
>

I think that depends entirely on the OS and tools you used to create the
bootable USB drive. In principle, the Qubes ISO should be the same as any ISO
in that respect. In other words: Whether your OS or tools keep metadata about
ISOs after you dd them somewhere is beyond the control of the ISO being
copied. The ISO is just a file, a blob of data. It can't control whether the
OS or tools manipulating it leave traces of it behind.

- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJXsmltAAoJENtN07w5UDAw/kAQAIUYrpSK4ReTC9c1zOWN6DRk
OuC1/D5dERTq1oD0nt/a7Ab6AEpkI4H29dT8U8F+wDF8RFm4OQyAR+gws83LHA4q
dgOPvoLjrXFY7BRwvqyuSvd8sc+Q3Diuajxla8mm8PUbT2IwhS77fPh1CjebYq7/
qhJ0DJhUq6AJqBUXJb8O425ipkWKDoCJOztq+cAbjfPaB290XoSTQWArfwtgTida
4xWlsCA0wBfB7hekWkPPSMwYZCxZpeHJyXKIuwycZQSiNdzn3lXRhhd5B8d5rGaM
D9y/By6XFdBhemsufauKSD2+fazn/nkCOea9PgdRsSbvk2r8JUsVU23hRUKgdvJV
1oWYMuFhKxp99euXnAQIqRg3lsuDeZ5r9XT47pB9tMHE75QszZ9GASWElZjMrzUr
sQjRnIxOCJhDuAgDRuJwMPUGzKtxat5GtXnWIgtcw01T49jC6cjbWzEqWb5LyEUO
8uw4GUXbG+PlrF/na0JR7I9tWICCUnAJg/hq6BguKi5IKP8wL0Hdzkg7TE684JJj
SL0Jr3kSp2UZgSc7p1fXdYARHwXuR+Htxi0KODU0QJP4bTd/pmqN2bYcteZ99lHR
3/RglJ7qinyGEYv/P9DlzO8eRAKwLZvNJ86O6lEvIV4id3mIajCCWzRIOCKBo5zp
3GU3SUzqMYV864M6DmhS
=Gt5S
-----END PGP SIGNATURE-----

[Andrew David Wong]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 2016-08-16 00:30, Adi Carlisle wrote:
> Ok ithis instance im dding from rufus/windows10 If i wipe metadata before i
> dd to disk will there be any after the write process?
>

I'm not sure what you mean by "wipe metadata before...." I suppose it depends
on what tool you use to do that, as well as what Rufus and Windows 10 do. I
don't think anyone here can answer that question definitively for you. It's
certainly far outside the scope of Qubes OS. You may want to ask the author of
Rufus. Better yet, consider using a privacy-respecting live OS to create the
bootable Qubes medium.

P.S. - Please keep the list CCed, and please don't top-post.

> On 16 Aug 2016 2:16 a.m., "Andrew David Wong" <a...@qubes-os.org> wrote:
>
> On 2016-08-15 02:31, adica...@gmail.com wrote:
>>>> Writing OS being where i dd from my old, potentially at risk OS
>>>>
>
> I think that depends entirely on the OS and tools you used to create the
> bootable USB drive. In principle, the Qubes ISO should be the same as any
> ISO in that respect. In other words: Whether your OS or tools keep
> metadata about ISOs after you dd them somewhere is beyond the control of
> the ISO being copied. The ISO is just a file, a blob of data. It can't
> control whether the OS or tools manipulating it leave traces of it behind.
>

- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJXszUuAAoJENtN07w5UDAwePwP/1wekXS+fWAN0dy7UgYFfsQg
vdfPn6mWb7DuFL0GIL8L97AD69JO2HxpjY9U8EJBe8SX0P6k43/DwO9cDPtMISaE
BujUOO5x6lJTR+r9Qpx1rnpw3Rifddm926YV6wlAbaQTOdYNt85vXs9R8aMTD+WG
U4V/vyzyIsbh8aNZF4ipXpjef1P9yRJX/wq414oV+HtzGsIlTvB9LqKI9dc/xegq
mUAwm8/RTj3eo9KfjdPXiXSbVE1/S2xfchxg28rlvrAfEEEoDhqqRaUd2kVg6fkO
Bp8NpaA+67/dSbhuCEdPXYN283+76dtN2pDoNhcAe9cSaeOfXnNvu5GrHGkmZq2D
JKahoJjj5L5YP9whxi762nE9Kapnmc62jLRhcJSdf5QO8k1LP665HIkx3Y307cr0
NVxGkOpDNw1vrZ03QI4jgJPVbs9fE6xEfn3Vdx2MBBFqzRJcp9Ol7bsroqwmhSyk
1/wQN7PY3/39R7VRDMbtuYXcaTX20U0pBAu7ZJDs1sNPfrS1iY2pM2+CKe85hTpz
+Duf7UDZWObiJYazq0JOqCU3Yik4lj/JbvtcLq300WViNfj28aK+zr8TSyTd/L69
ZK2g8e8JLl6RenbMrm8qd2MlfZiOIbI+jVoX3qfewWdq6ClcD+H7o8hSvxbkM6Rd
ng6Fkv9Iai2r2UbLbRdB
=R4Zg
-----END PGP SIGNATURE-----