On 04/21/2018 03:44 AM, Manuel Amador (Rudd-O) wrote:
On 2018-04-16 20:50, Jan Hustak wrote:
Hello,
I'm also open to discussing the basic concept: is it worth trying to
keep, for example, Firefox and GIMP in separate qubes, or should I
just relax and use one fat TemplateVM with the union of all
On 04/19/2018 10:00 AM, awokd wrote:
On Thu, April 19, 2018 5:45 am, Jan Hustak wrote:
I guess there's a cognitive aspect to it as well, not related to
security as such. I have over 2300 packages installed on my main Debian
notebook, many of them not needed anymore. Cleaning them out is a
On 2018-04-16 20:50, Jan Hustak wrote:
> Hello,
> I'm also open to discussing the basic concept: is it worth trying to
> keep, for example, Firefox and GIMP in separate qubes, or should I
> just relax and use one fat TemplateVM with the union of all packages I
> need?
>
Fat template with
On Thursday, April 19, 2018 at 4:00:55 AM UTC-4, awokd wrote:
> On Thu, April 19, 2018 5:45 am, Jan Hustak wrote:
>
> >
> > I guess there's a cognitive aspect to it as well, not related to
> > security as such. I have over 2300 packages installed on my main Debian
> > notebook, many of them not
I'm also not sure that separating large GUI apps from each other in
different VMs is an answer to anything; once you have the layers in
place to support one large app, you probably have most potential
app-related vulns installed at that point.
My personal recommendation is to use debian-9 for
However... in terms of flexible _and_ secure deployment of software,
Qubes could stand some improvement.
I wonder if there are compatible packaging systems that could be adapted
to modular app deployment per-VM. Something like 'snaps' might work.
And the deployment method could be an
On 04/16/2018 04:50 PM, Jan Hustak wrote:
Hello,
I really like Qubes' isolation approach. I would also like to isolate
the programs I run from code they don't need. So I want to split not
just my data into separate qubes, but also the software that works with
said data.
One way to do this
> However, The VM Manager insists on at least 10 GB for each qube. Giving
> up 100 GB with 75 GB empty (i.e. 15 % of total disk space) is steep. So my
> question is: how can I create smaller images for my qubes?
This is thin provisioned on disk, not dedicated. So you could give each VM
100GB,
Hello,
I really like Qubes' isolation approach. I would also like to isolate
the programs I run from code they don't need. So I want to split not
just my data into separate qubes, but also the software that works with
said data.
One way to do this is to install required software under
