Re: [qubes-users] Disposable VMs are not disposed of

2016-11-15 Thread Marek Marczykowski-Górecki
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Tue, Nov 15, 2016 at 02:37:14PM +, IX4 Svs wrote:
> On Tue, Nov 15, 2016 at 1:14 AM, Marek Marczykowski-Górecki <
> marma...@invisiblethingslab.com> wrote:
> 
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA256
> >
> > On Tue, Nov 15, 2016 at 12:34:19AM +, Alex wrote:
> > > This is the second time I encounter this freaky issue on R3.1:
> > >
> > > Start a DispVM Firefox, login to a website, close Firefox, observe the
> > disposable VM is gone from the VM manager. Fine so far.
> > >
> > > Launch a new disposable Firefox which creates a new VM with a different
> > name (dispN) - notice with horror that you are already logged on to the
> > website you had logged on to from the terminated VM.
> > >
> > > Surely this is not supposed to happen. How to troubleshoot?
> >
> > I believe you've hit this issue:
> > https://github.com/QubesOS/qubes-issues/issues/2200
> >
> > The issue is fixed in R3.2, but it hasn't been yet backported to R3.1...
> > For now, make sure that files in /var/lib/qubes/appvms/fedora-23-dvm (or
> > other - depending on what template you use for DispVM) are owned by your
> > user. Then recreate DispVM savefile with qvm-create-default-dvm.
> >
> >
> All files in /var/lib/qubes/appvms/fedora-23-dvm are owned by my user,
> group qubes - but volatile.img is -rw-r--r-- while all other files are
> -rw-rw-r-- (so, group can't write to it). I changed this with chmod 664
> volatile.img but on running qvm-create-default-vm the permissions are reset
> to their earlier state - and volatile.img is not group-writeable.
> 
> Should people on R3.1 just chmod 664 volatile.img right after recreating
> the DVM?

Above permissions looks ok - if the file is owned by your user, being
group writable does not matter. Maybe it was owned by root during
previous qvm-create-default-dvm call, but now is ok?

- -- 
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCAAGBQJYK5IvAAoJENuP0xzK19csYscH/RskSBghAdBbvwZm/UMc69RP
Raz6H3WRRRGCytN0Jfri+QiGWhQdugclWH2tyn9uUlzKFeNA4AE3GD7oT/bUc5Zf
8XJYV4JTWOEQN4TnfprDwksRQGyuPyfLAUUuiOyRqE2e2AaexXg7ZDTKNrQGG8qq
X0+pV3nE1U7Fw4WclGIohFb6PCtUR8ILvJ4fzODnH97V2K65qP3+/LqmryeEMTMu
2rr1VsI+y2CDjp3b6vOQQdyeWbaMa/OrkK7rXG+TS2SCV2g6C8UhCWBCMZ8OSWZZ
GEVrSH8yI0LgWSahbkN0biai68N+GDoGEFfKH/WkNhXBAUGr18Su6/R4FcIy0Ec=
=yyJR
-END PGP SIGNATURE-

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/20161115225439.GL17458%40mail-itl.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Disposable VMs are not disposed of

2016-11-15 Thread IX4 Svs
On Tue, Nov 15, 2016 at 1:14 AM, Marek Marczykowski-Górecki <
marma...@invisiblethingslab.com> wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On Tue, Nov 15, 2016 at 12:34:19AM +, Alex wrote:
> > This is the second time I encounter this freaky issue on R3.1:
> >
> > Start a DispVM Firefox, login to a website, close Firefox, observe the
> disposable VM is gone from the VM manager. Fine so far.
> >
> > Launch a new disposable Firefox which creates a new VM with a different
> name (dispN) - notice with horror that you are already logged on to the
> website you had logged on to from the terminated VM.
> >
> > Surely this is not supposed to happen. How to troubleshoot?
>
> I believe you've hit this issue:
> https://github.com/QubesOS/qubes-issues/issues/2200
>
> The issue is fixed in R3.2, but it hasn't been yet backported to R3.1...
> For now, make sure that files in /var/lib/qubes/appvms/fedora-23-dvm (or
> other - depending on what template you use for DispVM) are owned by your
> user. Then recreate DispVM savefile with qvm-create-default-dvm.
>
>
All files in /var/lib/qubes/appvms/fedora-23-dvm are owned by my user,
group qubes - but volatile.img is -rw-r--r-- while all other files are
-rw-rw-r-- (so, group can't write to it). I changed this with chmod 664
volatile.img but on running qvm-create-default-vm the permissions are reset
to their earlier state - and volatile.img is not group-writeable.

Should people on R3.1 just chmod 664 volatile.img right after recreating
the DVM?

Thanks

Alex

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/CAEe-%3DTcfU6%2B4L5KZOjCpaB5UQfo%2BjhoD-%2Bu5SgPoWHVqA-caiQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.