Re: [qubes-users] disposableVM not really disposable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Marek Marczykowski-Górecki: > On Fri, Aug 05, 2016 at 11:57:38AM +0200, Marek Marczykowski-Górecki wrote: >> On Wed, Jul 27, 2016 at 10:38:52AM +0100, cubit wrote: >>> 26. Jul 2016 23:14 by marma...@invisiblethingslab.com: >>> Check file list in /var/lib/qubes/appvms/fedora-23-dvm. Especially date and permissions of volatile.img there. >>> >>> >>> >>> >>> It's actually fedora-23-stable-dvm based off a copy of the template >>> >>> >>> >>> >>> Here is the file list, there is one noticeable difference when >>> comparing it to fedora-23-dvm folder.For my template >>> volatile.img is chmod 600 while it is 644 in fedora-23-dvm. >>> Changing the permissions to match 644 does not change anything, the >>> problem still exists @cubit: What is the output of 'sudo sh -c umask' in dom0? >> Change it to 664 (same as other files there) - so qubes group will have >> write access. > > What are permissions on the directory itself? > > >> (...) > >>> -rw-rw-r-- 1 user qubes1669 Jun 2 20:15 disp8.conf >>> -rw-rw-r-- 1 user qubes1670 Jun 2 20:15 disp9.conf >>> -rw-rw-r-- 1 user qubes 309223442 Jul 21 09:49 dvm-savefile >>> -rw-rw-r-- 1 user qubes1925 Jul 21 09:49 fedora-23-stable-dvm.conf >>> lrwxrwxrwx 1 user qubes 55 Mar 31 16:15 icon.png -> >>> /usr/share/icons/hicolor/128x128/devices/appvm-gray.png >>> -rw-rw-r-- 1 user qubes 1 Jul 21 09:49 netvm-id.txt >>> -rw-rw 1 user qubes 2147483648 Jul 21 09:49 private.img >>> -rw-rw-r-- 1 user qubes1024 Jul 21 09:49 saved-cows.tar >>> -rw--- 1 root qubes 12348030976 Jul 26 20:00 volatile.img >>> -rw-rw-r-- 1 user qubes 70 Mar 31 16:15 whitelisted-appmenus.list One case in which this happens is when the root user has a restrictive umask. Then prepare-volatile-img.sh creates a file as show above. qubes-prepare-saved-domain.sh then fails siletly to include volatile.img into saved-cows.tar. This can be simply fixed by not running prepare-volatile-img.sh as root (see attached patch, sudo is no longer necessary there). But I'm not sure if this is the problem in the reported cases. Especially this should be rather easily noticed since you can't start a dispvm when another is still running. What are the reasons for using bsdtar instead of tar? I tried to make the script to fail in this case but bsdtar justs prints a warning on permission errors and still exits with 0 (in contrast to GNU tar). -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJXpJl2AAoJEOSsySeKZGgWFFIQALrQQB4n7uGNpsbdlopX166W 8sqACeMwJ5eozMt8uZ0g6IalfCUW58YSKCYPtepUxN1I7S3hxVBHQcx0M3q2yxhJ LMmsAv7YdzFOxEr1oS+2UsmHJfuhCJjWMYEoIjTgskSVzB1Gd8vENptSPGUZedd9 IOYxfxIzahhx/2jYd5YdilqtW94Nr8iGCGVAqCnibE0oac16y5NTmSa4WP0gv4ou QBuj5ejm7VrUDbsexdzxOVR33AeGv4kize+PT23WDVM8Fjr3Nt60zUhFRVUY6eSD eSFmXw/re+KR9wweUiQBhtDk8WFFMkzSEBeh0Qxfs3SN7x2LeRLjIn+n5ns55TFA wIRMkfGykyAC9k468bkjcE4pUJs8EfTnKc6yNmFVn68Jxpip3R90hb4orgtdLEQc OeP7XERg/s78QDgjPod3CnroMKy7wTFQxsCgAFHpDiQKVNCSfQvGURMwcz/Mw37t +FAnCK85BMgKF0CsTHWoF+KXmTI5VqyrbfFElKHxtuJ+yQCJfWj0JyqudQ5Ff7Sd u9dZY1txUD5NJ3mPHISLRGzPEzdm/O1YDsNMEPu8ofGOK+fKDsQWlQWeXBVhD5pn 7SU/NXUvVjo5jK6Ii22QIch1IVehWdcjYahMpCOdZcR5kDoerksnYkWosUo/giO7 O2o/oh3+rIqIit705cTF =cWHQ -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/2065e306-d473-706a-a000-14c11ae76540%40ipsumj.de. For more options, visit https://groups.google.com/d/optout. From 469a88067fb724a27d8a912c398a4fa9ef9e46eb Mon Sep 17 00:00:00 2001 From: HW42Date: Fri, 5 Aug 2016 15:44:05 +0200 Subject: [PATCH] prepare-volatile-img.sh: don't run as root This is no longer necessary since volatile.img is formated inside the VM. This also fixes DispVM creation if the user sets a restrictive umask for root. Maybe related to #2200. --- linux/aux-tools/prepare-volatile-img.sh | 4 1 file changed, 4 deletions(-) diff --git a/linux/aux-tools/prepare-volatile-img.sh b/linux/aux-tools/prepare-volatile-img.sh index 40e22f5..b32142b 100755 --- a/linux/aux-tools/prepare-volatile-img.sh +++ b/linux/aux-tools/prepare-volatile-img.sh @@ -1,9 +1,5 @@ #!/bin/sh -if [ "`id -u`" != "0" ]; then - exec sudo $0 $* -fi - set -e if ! echo $PATH | grep -q sbin; then -- 2.8.1 0001-prepare-volatile-img.sh-don-t-run-as-root.patch.sig Description: PGP signature
Re: [qubes-users] disposableVM not really disposable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wed, Jul 27, 2016 at 10:38:52AM +0100, cubit wrote: > 26. Jul 2016 23:14 by marma...@invisiblethingslab.com: > > > Check file list in /var/lib/qubes/appvms/fedora-23-dvm. Especially date > > and permissions of volatile.img there. > > > > > > > It's actually fedora-23-stable-dvm based off a copy of the template > > > > > Here is the file list, there is one noticeable difference when comparing it > to fedora-23-dvm folder. For my template volatile.img is chmod 600 while > it is 644 in fedora-23-dvm. Changing the permissions to match 644 does not > change anything, the problem still exists Change it to 664 (same as other files there) - so qubes group will have write access. (...) > -rw-rw-r-- 1 user qubes 1669 Jun 2 20:15 disp8.conf > -rw-rw-r-- 1 user qubes 1670 Jun 2 20:15 disp9.conf > -rw-rw-r-- 1 user qubes 309223442 Jul 21 09:49 dvm-savefile > -rw-rw-r-- 1 user qubes 1925 Jul 21 09:49 fedora-23-stable-dvm.conf > lrwxrwxrwx 1 user qubes 55 Mar 31 16:15 icon.png -> > /usr/share/icons/hicolor/128x128/devices/appvm-gray.png > -rw-rw-r-- 1 user qubes 1 Jul 21 09:49 netvm-id.txt > -rw-rw 1 user qubes 2147483648 Jul 21 09:49 private.img > -rw-rw-r-- 1 user qubes 1024 Jul 21 09:49 saved-cows.tar > -rw--- 1 root qubes 12348030976 Jul 26 20:00 volatile.img > -rw-rw-r-- 1 user qubes 70 Mar 31 16:15 whitelisted-appmenus.list - -- 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 iQEbBAEBCAAGBQJXpGMTAAoJENuP0xzK19cs3nQH92oO91qw15Sa0f8jTAWbFtGX pzVsXwH2i5jd9ctMufe6kqzAua32Bhuzyouj89F5XfD2CHUGpIA6W998P46RtxNG FGDpyT20gKSpdfZlfpwwZGDlDCp4cbfiep15cSnC+yLhr8knTUBTlP+co9rXUyhk 7a/Ut7C8YknTLogkuHl7zfwodpi6ZUS+Iae4/4H2BJKMTeTS+Z0/OgpQUuI8aOXH oESm6aTqkcrync2kLx8XZBkaBoXWdgj7W/Ram4bKNUO6p+k7oA7DrnpwRNsikt3M 0g0Yx97AN6qeZfsUgjqP219GqM0AqzN55k6nfLDkn12HkJSbLh+a5bvlY9LPuQ== =pj6H -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/20160805095738.GN32095%40mail-itl. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] disposableVM not really disposable
Same issue here. Solved by entering on the template fedora-23-dispvm (or the name you are using) I have opened FF for addon updates. run command touch. qubes-disp.customized as you can find here https://www.qubes-os.org/doc/dispvm-customization/ Than use the command qvm-create-default-dvm And you should start with empty tempaltes. Hope it help you On 07/27/2016 11:38 AM, cubit wrote: > 26. Jul 2016 23:14 by marma...@invisiblethingslab.com: > >> Check file list in /var/lib/qubes/appvms/fedora-23-dvm. Especially date >> and permissions of volatile.img there. >> > > > > > It's actually fedora-23-stable-dvm based off a copy of the template > > > > > Here is the file list, there is one noticeable difference when comparing it > to fedora-23-dvm folder.For my template volatile.img is chmod 600 while > it is 644 in fedora-23-dvm. Changing the permissions to match 644 does not > change anything, the problem still exists > > > > > > total 503544 > -rw-rw-r-- 1 user qubes1671 Jun 3 11:18 disp10.conf > -rw-rw-r-- 1 user qubes1671 Jun 3 11:33 disp11.conf > -rw-rw-r-- 1 user qubes1671 Jun 4 19:58 disp12.conf > -rw-rw-r-- 1 user qubes1671 Jun 4 19:59 disp13.conf > -rw-rw-r-- 1 user qubes1671 Jun 4 20:01 disp14.conf > -rw-rw-r-- 1 user qubes1671 Jul 14 18:25 disp15.conf > -rw-rw-r-- 1 user qubes1671 Jul 14 18:26 disp16.conf > -rw-rw-r-- 1 user qubes1671 Jul 14 18:27 disp17.conf > -rw-rw-r-- 1 user qubes1671 Jul 14 18:28 disp18.conf > -rw-rw-r-- 1 user qubes1671 Jul 14 18:34 disp19.conf > -rw-rw-r-- 1 user qubes1669 Jul 26 15:08 disp1.conf > -rw-rw-r-- 1 user qubes1671 Jul 14 18:53 disp20.conf > -rw-rw-r-- 1 user qubes1671 Jul 15 12:44 disp21.conf > -rw-rw-r-- 1 user qubes1671 Jul 17 07:27 disp22.conf > -rw-rw-r-- 1 user qubes1671 Jul 18 08:55 disp23.conf > -rw-rw-r-- 1 user qubes1671 Jul 18 09:20 disp24.conf > -rw-rw-r-- 1 user qubes1671 Jul 18 13:30 disp25.conf > -rw-rw-r-- 1 user qubes1671 Jul 18 16:25 disp26.conf > -rw-rw-r-- 1 user qubes1671 Jul 18 20:48 disp27.conf > -rw-rw-r-- 1 user qubes1671 Jul 18 20:56 disp28.conf > -rw-rw-r-- 1 user qubes1671 Jul 19 11:47 disp29.conf > -rw-rw-r-- 1 user qubes1669 Jul 26 15:58 disp2.conf > -rw-rw-r-- 1 user qubes1671 Jul 19 15:23 disp30.conf > -rw-rw-r-- 1 user qubes1671 Jul 19 15:31 disp31.conf > -rw-rw-r-- 1 user qubes1671 Jul 19 15:35 disp32.conf > -rw-rw-r-- 1 user qubes1671 Jul 19 15:36 disp33.conf > -rw-rw-r-- 1 user qubes1671 Jul 19 15:44 disp34.conf > -rw-rw-r-- 1 user qubes1671 Jul 19 15:52 disp35.conf > -rw-rw-r-- 1 user qubes1671 Jul 19 16:19 disp36.conf > -rw-rw-r-- 1 user qubes1671 Jul 19 17:02 disp37.conf > -rw-rw-r-- 1 user qubes1671 Jul 19 17:14 disp38.conf > -rw-rw-r-- 1 user qubes1671 Jul 19 18:13 disp39.conf > -rw-rw-r-- 1 user qubes1669 Jul 26 17:25 disp3.conf > -rw-rw-r-- 1 user qubes1671 Jul 19 20:07 disp40.conf > -rw-rw-r-- 1 user qubes1671 Jul 20 08:07 disp41.conf > -rw-rw-r-- 1 user qubes1671 Jul 20 16:30 disp42.conf > -rw-rw-r-- 1 user qubes1671 Jul 21 09:49 disp43.conf > -rw-rw-r-- 1 user qubes1671 Jul 21 12:00 disp44.conf > -rw-rw-r-- 1 user qubes1671 Jul 21 12:01 disp45.conf > -rw-rw-r-- 1 user qubes1671 Jul 21 12:02 disp46.conf > -rw-rw-r-- 1 user qubes1671 Jul 21 12:05 disp47.conf > -rw-rw-r-- 1 user qubes1671 Jul 21 12:05 disp48.conf > -rw-rw-r-- 1 user qubes1671 Jul 21 12:06 disp49.conf > -rw-rw-r-- 1 user qubes1669 Jul 26 18:34 disp4.conf > -rw-rw-r-- 1 user qubes1671 Jul 21 14:15 disp50.conf > -rw-rw-r-- 1 user qubes1671 Jul 21 15:09 disp51.conf > -rw-rw-r-- 1 user qubes1671 Jul 22 09:23 disp52.conf > -rw-rw-r-- 1 user qubes1671 Jul 22 09:24 disp53.conf > -rw-rw-r-- 1 user qubes1669 Jul 26 18:51 disp5.conf > -rw-rw-r-- 1 user qubes1669 Jul 26 19:59 disp6.conf > -rw-rw-r-- 1 user qubes1669 May 30 12:16 disp7.conf > -rw-rw-r-- 1 user qubes1669 Jun 2 20:15 disp8.conf > -rw-rw-r-- 1 user qubes1670 Jun 2 20:15 disp9.conf > -rw-rw-r-- 1 user qubes 309223442 Jul 21 09:49 dvm-savefile > -rw-rw-r-- 1 user qubes1925 Jul 21 09:49 fedora-23-stable-dvm.conf > lrwxrwxrwx 1 user qubes 55 Mar 31 16:15 icon.png -> > /usr/share/icons/hicolor/128x128/devices/appvm-gray.png > -rw-rw-r-- 1 user qubes 1 Jul 21 09:49 netvm-id.txt > -rw-rw 1 user qubes 2147483648 Jul 21 09:49 private.img > -rw-rw-r-- 1 user qubes1024 Jul 21 09:49 saved-cows.tar > -rw--- 1 root qubes 12348030976 Jul 26 20:00 volatile.img > -rw-rw-r-- 1 user qubes 70 Mar 31 16:15 whitelisted-appmenus.list > > > > > -- You received this message because you are subscribed to the Google
Re: [qubes-users] disposableVM not really disposable
26. Jul 2016 23:14 by marma...@invisiblethingslab.com: > Check file list in /var/lib/qubes/appvms/fedora-23-dvm. Especially date > and permissions of volatile.img there. > It's actually fedora-23-stable-dvm based off a copy of the template Here is the file list, there is one noticeable difference when comparing it to fedora-23-dvm folder. For my template volatile.img is chmod 600 while it is 644 in fedora-23-dvm. Changing the permissions to match 644 does not change anything, the problem still exists total 503544 -rw-rw-r-- 1 user qubes 1671 Jun 3 11:18 disp10.conf -rw-rw-r-- 1 user qubes 1671 Jun 3 11:33 disp11.conf -rw-rw-r-- 1 user qubes 1671 Jun 4 19:58 disp12.conf -rw-rw-r-- 1 user qubes 1671 Jun 4 19:59 disp13.conf -rw-rw-r-- 1 user qubes 1671 Jun 4 20:01 disp14.conf -rw-rw-r-- 1 user qubes 1671 Jul 14 18:25 disp15.conf -rw-rw-r-- 1 user qubes 1671 Jul 14 18:26 disp16.conf -rw-rw-r-- 1 user qubes 1671 Jul 14 18:27 disp17.conf -rw-rw-r-- 1 user qubes 1671 Jul 14 18:28 disp18.conf -rw-rw-r-- 1 user qubes 1671 Jul 14 18:34 disp19.conf -rw-rw-r-- 1 user qubes 1669 Jul 26 15:08 disp1.conf -rw-rw-r-- 1 user qubes 1671 Jul 14 18:53 disp20.conf -rw-rw-r-- 1 user qubes 1671 Jul 15 12:44 disp21.conf -rw-rw-r-- 1 user qubes 1671 Jul 17 07:27 disp22.conf -rw-rw-r-- 1 user qubes 1671 Jul 18 08:55 disp23.conf -rw-rw-r-- 1 user qubes 1671 Jul 18 09:20 disp24.conf -rw-rw-r-- 1 user qubes 1671 Jul 18 13:30 disp25.conf -rw-rw-r-- 1 user qubes 1671 Jul 18 16:25 disp26.conf -rw-rw-r-- 1 user qubes 1671 Jul 18 20:48 disp27.conf -rw-rw-r-- 1 user qubes 1671 Jul 18 20:56 disp28.conf -rw-rw-r-- 1 user qubes 1671 Jul 19 11:47 disp29.conf -rw-rw-r-- 1 user qubes 1669 Jul 26 15:58 disp2.conf -rw-rw-r-- 1 user qubes 1671 Jul 19 15:23 disp30.conf -rw-rw-r-- 1 user qubes 1671 Jul 19 15:31 disp31.conf -rw-rw-r-- 1 user qubes 1671 Jul 19 15:35 disp32.conf -rw-rw-r-- 1 user qubes 1671 Jul 19 15:36 disp33.conf -rw-rw-r-- 1 user qubes 1671 Jul 19 15:44 disp34.conf -rw-rw-r-- 1 user qubes 1671 Jul 19 15:52 disp35.conf -rw-rw-r-- 1 user qubes 1671 Jul 19 16:19 disp36.conf -rw-rw-r-- 1 user qubes 1671 Jul 19 17:02 disp37.conf -rw-rw-r-- 1 user qubes 1671 Jul 19 17:14 disp38.conf -rw-rw-r-- 1 user qubes 1671 Jul 19 18:13 disp39.conf -rw-rw-r-- 1 user qubes 1669 Jul 26 17:25 disp3.conf -rw-rw-r-- 1 user qubes 1671 Jul 19 20:07 disp40.conf -rw-rw-r-- 1 user qubes 1671 Jul 20 08:07 disp41.conf -rw-rw-r-- 1 user qubes 1671 Jul 20 16:30 disp42.conf -rw-rw-r-- 1 user qubes 1671 Jul 21 09:49 disp43.conf -rw-rw-r-- 1 user qubes 1671 Jul 21 12:00 disp44.conf -rw-rw-r-- 1 user qubes 1671 Jul 21 12:01 disp45.conf -rw-rw-r-- 1 user qubes 1671 Jul 21 12:02 disp46.conf -rw-rw-r-- 1 user qubes 1671 Jul 21 12:05 disp47.conf -rw-rw-r-- 1 user qubes 1671 Jul 21 12:05 disp48.conf -rw-rw-r-- 1 user qubes 1671 Jul 21 12:06 disp49.conf -rw-rw-r-- 1 user qubes 1669 Jul 26 18:34 disp4.conf -rw-rw-r-- 1 user qubes 1671 Jul 21 14:15 disp50.conf -rw-rw-r-- 1 user qubes 1671 Jul 21 15:09 disp51.conf -rw-rw-r-- 1 user qubes 1671 Jul 22 09:23 disp52.conf -rw-rw-r-- 1 user qubes 1671 Jul 22 09:24 disp53.conf -rw-rw-r-- 1 user qubes 1669 Jul 26 18:51 disp5.conf -rw-rw-r-- 1 user qubes 1669 Jul 26 19:59 disp6.conf -rw-rw-r-- 1 user qubes 1669 May 30 12:16 disp7.conf -rw-rw-r-- 1 user qubes 1669 Jun 2 20:15 disp8.conf -rw-rw-r-- 1 user qubes 1670 Jun 2 20:15 disp9.conf -rw-rw-r-- 1 user qubes 309223442 Jul 21 09:49 dvm-savefile -rw-rw-r-- 1 user qubes 1925 Jul 21 09:49 fedora-23-stable-dvm.conf lrwxrwxrwx 1 user qubes 55 Mar 31 16:15 icon.png -> /usr/share/icons/hicolor/128x128/devices/appvm-gray.png -rw-rw-r-- 1 user qubes 1 Jul 21 09:49 netvm-id.txt -rw-rw 1 user qubes 2147483648 Jul 21 09:49 private.img -rw-rw-r-- 1 user qubes 1024 Jul 21 09:49 saved-cows.tar -rw--- 1 root qubes 12348030976 Jul 26 20:00 volatile.img -rw-rw-r-- 1 user qubes 70 Mar 31 16:15 whitelisted-appmenus.list -- 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/KNfi86l--3-0%40tutanota.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] disposableVM not really disposable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Tue, Jul 26, 2016 at 07:29:10PM +0100, cubit wrote: > 26. Jul 2016 18:26 by a...@qubes-os.org: > > > Another user, Alex, previously reported the same phenomenon here: > > > > https://groups.google.com/d/topic/qubes-users/Eipv3eNKzJQ/discussion > > > > Thank you, my search fu was failing me, I though I remembered something like > this already > > > I've begun tracking this issue here: > > > > https://github.com/QubesOS/qubes-issues/issues/2200 > > > > We currently know very little about this issue, so I'm afraid there is > > no solution yet. > > Is there any information I can gather that might help before I run > qvm-create-defalult-dvm? Check file list in /var/lib/qubes/appvms/fedora-23-dvm. Especially date and permissions of volatile.img there. - -- 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 iQEcBAEBCAAGBQJXl+66AAoJENuP0xzK19csa+4IAIwrFubD3JWRprTv9ZrvbwnT w0iiOFNig3JQplN5HUsG4MBd+4lkBUmCvjuWPccCTh4nuzJWFJT7VccL/fgs6vUk Zhj4RQzugFjhn21+aiHvE/dgNJDwrMGx/AxW/kt2oeOJ/ITdOuBRCLs1eVKiKe02 xdyxKgq1paCqQILHb8o7j6hstdhyOwjpicGZz/BYTzG1ZuwCNHZ9rIlsHyUxYWgh q75YnDK67vbeVQ0cvuhfgcmSkgR2RpbjxI+hZJL2ddJ6USyegr9nuPbUAwKLww+w RZO8i9amwVtNYWpcUbKWx9RlrUQAgJOZ3+apecqaAHC+V6wU0dFluIBGrGzf+uA= =DEa+ -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/20160726231402.GN32095%40mail-itl. For more options, visit https://groups.google.com/d/optout.
[qubes-users] disposableVM not really disposable
Heyya I have discovered my disposableVM Firefox is not really disposable as history persists between sessions. This came to notice as I have recently customized my browser, setting up a new start page and removing the hello and pocket buttons. Though I have noticed similar issues before customization though did not think to check if history was being stored. Over the last couple of days each time I start Firefox I get the "Well, this is embarrassing." error with a restore session tab for my home page. I also get two other tabs to Mozilla pages => The first run page and a bit ironically a page showing the private browsing mode. I opened the history tab today to discover I have 3 days worth of history stored in the browser. I can work around this by doing a qvm-create-defalult-dvm but I would like to know what is the best way to fix this permanently. -- 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/KNcK_Oi--3-0%40tutanota.com. For more options, visit https://groups.google.com/d/optout.