On 7/12/23 8:47 AM, Metatron wrote: > [...] > > An additonal use case is that I occationaly build a qube for friends and > then send to them, again the mandatory encryption is an annoyance. I > could also imagine that at some point qubes users may even want to > "publish" a qube publicly. > > [...] >
It's worth noting that every Qubes backup includes a qubes.xml file that lists all the qubes in the system at the time the backup was created regardless of whether those qubes were selected for inclusion in the backup. This is an intentional aspect of the design of qvm-backup[-restore], the goal of which is to preserve the system's data and configuration as well as possible, which requires the inclusion of data about the dependencies of each qube in the backup on other qubes. [1] There's an open issue for the development of a separate export tool intended for the specific use case you describe. [2] [1] https://github.com/QubesOS/qubes-issues/issues/2645#issuecomment-281720735 [2] https://github.com/QubesOS/qubes-issues/issues/1747 -- You received this message because you are subscribed to the Google Groups "qubes-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-devel/fe0e522d-9588-babe-cfa7-28258ab6643a%40qubes-os.org.
