Perhaps it would.
Most likely not.
Take a simple example - I use Qubes for work: searching the net for
information, writing reports, and email.
I could do this in a single qube.
Where is the risk? A malicious web site could be an attack vector - if
successful the attacker could have access to email, and to my reports.
Perhaps I decide to improve things by using disposables for the net searching.
I have not removed the risk, but I have reduced it. Now a malicious site
would have to set an attack that included inter-qube processes.
Where is the risk? A malicious email could be an attack vector - if
successful the attacker could have access to my reports and all email.
I decide to use a separate qube for my email - perhaps I use split mail,
and open attachments in offline disposables.
Now I have a qube for email (perhaps more if I use split mail); a qube
where I write reports, disposables for net searching, and I open
email attachments in offline disposables.
It makes some sense to have a separate repository shared between
these different qubes - I could copy information from the net, and
from email, directly in to the report qube, or I could separate storage
from use. I can use qrexec policies to control what access these qubes
have to the shared archive.
Separating out activities in to these different qubes has helped reduce
Where is the risk? Malicious content? Content is not accessed except in
disposables. At this stage I don’t care if I have malicious files
stored in the shared archive, because I do not open it there, but I
can still access the content.
I decide to separate image processing from data processing, using
distinct disposables, based on minimal templates.
If I intend to share the files, then I use native Qubes tools
qvm-convert-pdf) to sanitise them. I may also
use a scanner qube.
Now I have quite a few qubes: I use qrexec policies to control the
I never presume to speak for the Qubes team.
flow of information, and
mimeapps to make sure that files open in the
Many qubes interact with the same file from the shared archive.
Still risk, but reduced: and we can go further, as we identify risk and
try to mitigate it.
Qubes tools and policies let you build this as you will.
When I comment in the Forum or in the mailing lists I speak for myself.