Re: [qubes-users] Fetching updates after disabling qubes-update-check in clearnet qubes
On Wednesday, 15 July 2020 05:10:30 UTC+8, awokd wrote: > > > In either case, don't forget to have a line in > /etc/qubes-rpc/policy/qubes.UpdatesProxy like: > > $type:TemplateVM $default allow,target=sys-whonix > > I didn't know about this, so this helps haaber's comment make a lot more sense. Thank you both -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/75498f0d-c982-4d57-a989-35062a88eaf8o%40googlegroups.com.
Re: [qubes-users] Post Fedora-32 Template Installation
On 7/14/20 9:57 PM, Qubes wrote: I installed a clean Fedora-32 template today, but I have some issues and I am not sure where to start. After installing the F-32 template I switched the default-mgmt-dvm qube to use the F-32 template. I then created a new qube basing it on the F-32 template, test-fedora-32-template, just to check that everything is working ok on this test vm before changing all of my F-31 based qubes over to F-32. I am unable to boot the test-fedora-32-template qube. After a while I receive a system notification, the ones that pop up top right of the screen, saying, 'Cannot connect to qrexec agent for 60 seconds, see /var/log/xen/console/guest-test-fedora-32-template.log for details' and if I look in the log file I see hundreds of messages like this... '.Failed to fork() worker: Cannot allocate memory' '.systemd-udevd[272]: xvdc1: Failed to process device, ignoring: No space left on device' '.eth0: Failed to process device, ignoring: No space left on device' The F-32 template itself starts up without any problems. The problem described above definitely has something to do with the f-32 specifically. Even after changing my test qube to the f-31 template and starting it the qube still refuses to boot and gives me the same issues in /var/log/xen/console/guest-test-fedora-32-template.log. However, if I create a new qube based on my f-31 template then everything works as expected. The after effect of this is also, because I changed my default-mgmt-dvm to the f-32 template, in order to update the f-32 template, which subsequently failed because machines based on the f-32 template don't work, my default-mgmt-dvm is also bust. I guess I can recreate it, but that still does not solve my f-32 problems. AND, all of these issues started when I accidentally interrupted the f-32-minimal template installation as I described in a previous email to this group 'Template Installation Problem'. In the meantime I have managed to get the minimal template installed using the --action=reinstall option as described in the documentation. 'sudo qubes-dom0-update --action=reinstall qubes-template-fedora-32-minimal' Following on from my previous email I also had to reinstall the f-32 template because it gave the same issues I I describe here now. I hoped that reinstalling the template would fix the issues, but they appear deeper than the template. I really hoped I would be able to fix this without having to resort to using a full system backup and starting from 'scratch'. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/3c1d6618-ba7a-2854-2be6-eb3eb7e48c91%40ak47.co.za.
Re: [qubes-users] Re: DisposableVM Help
Robert Spigler: > How would I go about properly creating a fedora-32-dvm with the > 'template_for_dvms' flag set? https://www.qubes-os.org/doc/disposablevm-customization/ -- - don't top post Mailing list etiquette: - trim quoted reply to only relevant portions - when possible, copy and paste text instead of screenshots -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/7718f51e-31fc-3734-bf71-47501bca04ca%40danwin1210.me.
Re: [qubes-users] Fetching updates after disabling qubes-update-check in clearnet qubes
haaber: >> <<--snip-->> >> Though it's not clear to me whether this is actually an issue, I figured >> I'd do it anyways. My question is, if I wanted to disable >> qubes-update-check service, how would I go about updating my templates >> over tor? Do I create debian and fedora templates linked to sys-whonix >> just to get updates? > > AFAIK the updates themselves run over sys-whonix by default. So, if you > run e.g. "apt-get update" on your debian-10 template, this connection > goes over tor. However, the notification about updates to run (yellow > update wheel widget in the right top corner) goes by standard over > the AppVM and so, most of the time over the clear (as your clock, that > updates over sys-net). > > Since user-action is required (by running the update widget, or, as me, > doing it all by hand), the notification is rather uncorrelated to the > download action, I second Marek here. > > It is, as always, a convenience-vs-security question. You may uninstall > the qubes-update-check service and run (checks for) updates by hand (or > script) periodically in your template-VMs. The gain is small, the pain > is high, so most people don't do it. That is my pov, maybe there is some > contradicting one? > In either case, don't forget to have a line in /etc/qubes-rpc/policy/qubes.UpdatesProxy like: $type:TemplateVM $default allow,target=sys-whonix . -- - don't top post Mailing list etiquette: - trim quoted reply to only relevant portions - when possible, copy and paste text instead of screenshots -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/3488ef52-ec01-ddd5-eb7f-fb89207703e8%40danwin1210.me.
Re: [qubes-users] Trouble installing Whonix 15
shamaarmarti...@gmail.com: > I wanted to use the uninstall reinstall method to upgrade whonix 14 to 15 on > qubes 4.0 > > Procedure: > 1. Delete all whonix template packages > 2. Make sure dom0 is updated > 3. Adjust whonix version to 15 > 4. Attempt to download and configure TemplateVMs with the command: > sudo qubesctl state.sls qvm.anon-whonix > > Results: various errors > virtual machine does not exist! > Got empty response from qubessd > 7 succeeded > 6 Failed > Try installing the whonix-gw-15 and whonix-ws-15 templates manually, then run that Salt command again. -- - don't top post Mailing list etiquette: - trim quoted reply to only relevant portions - when possible, copy and paste text instead of screenshots -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/3300deac-7785-00d9-5fb0-94e94c843202%40danwin1210.me.
Re: [qubes-users] Re: Does qubes protect against all firmware viruses ?
tomas.schutz...@gmail.com: > I am still looking into this, it is a lot of to think of. Do you know any > sites where is threat modeling for average user? I was trying dozens of > phrases... and i didn't find any threat model website. Everything only for > companies and developers, which were completely useless, i even banned > these words in my search... > "Threat model" is a generic security term. See https://www.macobserver.com/tips/how-to/security-build-threat-model/ for a short example of how to develop one. Very basically, identify what you want to protect, and against who/what. Then you can identify means to defend it. -- - don't top post Mailing list etiquette: - trim quoted reply to only relevant portions - when possible, copy and paste text instead of screenshots -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/e1d80bef-3c53-c54c-35f2-ad1862c4ad61%40danwin1210.me.
Re: [qubes-users] Can’t get rid off black screen
shamaarmarti...@gmail.com: > I turned off auto start rebooted turned it back on rebooted again. Now I have > what appears to be a command screen but I can’t interact with it. The screen > is blocking the qubes icon and I keep restarting it and it’s lets me type for > a second then disappears back to a black screen. I would reinstall but I > didn’t back up the wallet on this qube. Any advice would be helpful. Thanks. > What does auto start have to do with it; are you only getting the black screen when you start a certain VM? -- - don't top post Mailing list etiquette: - trim quoted reply to only relevant portions - when possible, copy and paste text instead of screenshots -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/472fe1da-d349-77e0-ca02-ca1c8c2219f8%40danwin1210.me.
[qubes-users] Re: pen testing / port forwarding guide?
On 2020-07-14 16:54, 'J.M. Porup' via qubes-users wrote: hi, Has anyone written a guide to setting up a Kali vm in Qubes for pen testing? I'm studying for the OSCP, and the Qubes firewall port forwarding guide suggests a fragile and finicky setup that I'm reluctant to rely on. Punching holes from sys-net to sys-firewall to vpn-vm to an an appvm just to run `nc -nlvp ` seems... like a kludge, at best. Issue #4028 tracks this problem. The alternatives seem to be 1) create a HVM with direct access to hardware--no sys-net or firewall-vm--or 2) purchase a dedicated laptop for this use case. Any suggestions? thanks, jmp I've been using this script for a long time for port forwarding: https://gist.github.com/Joeviocoe/6c4dc0c283f6d6c5b1a3f5af8793292b This one might also be useful: https://gist.github.com/Joeviocoe/90ec9fd9a0769b4671a8ae9c87584187 Best. P. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/2de40b8b-74ea-a933-cbc7-8869eee7b7ca%40gmx.de.
Re: [qubes-users] Reattaching PCI device to dom0 via console. Error in documentation.
alexhisf via qubes-users: > > The solution at > http://qubesosfasa4zl44o4tws22di6kepyzfeqv3tg4e3ztknltfxqrymdad.onion/doc/pci-devices/ > Bringing PCI Devices Back to dom0 > echo > /sys/bus/pci/drivers/pciback/unbindMODALIAS=`cat > /sys/bus/pci/devices//modalias`MOD=`modprobe -R $MODALIAS | head -n > 1`echo > /sys/bus/pci/drivers/$MOD/bind > is not working. > 1st string - successful > 2nd string - successful > 3rd string - successful > 4th string - error: -bash: /sys/bus/pci/drivers/$MOD/bind : Ambiguous redirect > 4th string causes error and not working, so impossible to reattach pci device > via console. > > Previously i attached my (Primary) GPU to whonix-ws-15. When i clicked to > start whonix-ws-15 my PC has reboot. Now after password entering while > booting the system, monitor vision disappearing after few minutes. OS is > booting normally but without monitor view. > I switched off system. Inserted 2nd Graphic card and when OS booted i can > recieve view from 2nd graphic card but only in console mode. And i can not > reattach my 1st Graphic card to dom0 because of represented error. qvm-pci > always shows my card at whonix-ws-15. Meanwhile whonix-ws-15 switched to > start while system booting but it doesn't.Thank you. > Try removing the graphic card via qvm-pci or from whonix-ws-15 Qube Settings/Devices. -- - don't top post Mailing list etiquette: - trim quoted reply to only relevant portions - when possible, copy and paste text instead of screenshots -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/452ea85c-0647-e1b2-e138-bac9bf4caee8%40danwin1210.me.
Re: [qubes-users] Re: need help or support
Frédéric Pierret: > Hi > > On 2020-07-07 11:50, david russo wrote: >> The main issu is when I want to use internet acces as Firefox comboned with >> TOR, I checked my IP on the websit « monip » and Nothing change, tor doesn’t >> support the hide IP. If I understand you right, you are using Firefox to browse to monip and it shows your real IP, not a Tor one. Make sure you are using the right Firefox. If you have a fresh install of Qubes, try the one in Disposable: whonix-ws-15-dvm/TorBrowser (Anondist). -- - don't top post Mailing list etiquette: - trim quoted reply to only relevant portions - when possible, copy and paste text instead of screenshots -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/1822b3dc-16ca-ab39-404c-5e0445ba87db%40danwin1210.me.
Re: [qubes-users] Verifying VM updates and packages
E. Foster: > Or do some updates occur because a template VM has been changed in a > repository, and the update package is then pushed to the respective VMs > using the template? This. Qubes Updater (Qubes menu/System Tools) runs periodically and checks for updates in repos. > Bizarrely, I have a VM and Template VM that keeps requesting to be updated > and fails. Try updating the template from a terminal session on it. > And lastly, how many times can a device be rebooted before you should be > concerned about Xen issues. Until the hardware fails, I guess. Unless you're talking about hard power offs, in which case I'd be most concerned about file system corruption over any Xen issues. -- - don't top post Mailing list etiquette: - trim quoted reply to only relevant portions - when possible, copy and paste text instead of screenshots -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/81043d0a-e113-c1d3-eb3e-9db0191a9377%40danwin1210.me.
[qubes-users] Re: pen testing / port forwarding guide?
tirsdag den 14. juli 2020 kl. 17.54.43 UTC+2 skrev jm: > > hi, > > Has anyone written a guide to setting up a Kali vm in Qubes for > pen testing? > I have Kali rolling installed and happy using it for CTF gaming and small stuff. I love Qubes and Kali together, but for reverse shell, etc. Andrew Douma wrote en evaluation some time ago, and recommended not using Qubes for pentesting. https://medium.com/@securitystreak/living-with-qubes-os-r3-2-rc3-for-a-week-1a37e04c799e https://medium.com/@securitystreak/buying-a-professional-penetration-testing-laptop-for-2017-6cd21e65dc2 https://medium.com/hackernoon/the-2017-pentester-guide-to-windows-10-privacy-security-cf734c510b8d > I'm studying for the OSCP, and the Qubes firewall port forwarding > guide suggests a fragile and finicky setup that I'm reluctant to > rely on. Punching holes from sys-net to sys-firewall to vpn-vm to > an an appvm just to run `nc -nlvp ` seems... like a kludge, at > best. > > Issue #4028 tracks this problem. > > The alternatives seem to be 1) create a HVM with direct access > to hardware--no sys-net or firewall-vm--or 2) purchase a > dedicated laptop for this use case. > Both suggestions are good, I believe. Sincerely Max -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/8998a7df-2182-47f5-ad12-e69107a9bab2o%40googlegroups.com.
Re: [qubes-users] LUKS passphrase failures
joshkane...@gmail.com: > Booting into Kali (forensics mode) and unlocking the ssd failed. > > I typed out the passphrase to a text document, confirmed it was correct, > and pasted it into the prompt. > > "incorrect passphrase" > > This implies to me that the header was altered in some way. 2 days ago, my > battery has completely died...and my laptop is now for all intents and > purposes a desktop. Would that kind of power issue affect the ssd in such > a way as to alter the header? > > I regret not having a backup or hash of the headernot so much to > recover data, but at this point, to see if it has been altered...or if the > passphrase itself was changed somehow...but I'd rather not go down that > rabbit-hole of paranoia. > > There is always the slim chance I am continuing to miss-type > somethingafter all. > > On Sunday, July 5, 2020 at 6:03:12 PM UTC-4, haaber wrote: >> >> >>> I have tried this process with the other kernel options available as >>> well, to no avail. >>> >>> Any help or advice (successful or not) is appreciated. >> >> sounds daunting. So did you use a live-linux that has luks 'onboard' >> (like tails) ? That way you could distinguish between luks problems and >> qubes problems. It would also allow emergency backups before trying to >> unbug the actual qubes installation (for that question I cannot help). >> Do not play around before data is safe, or, if you can't resist, don't >> complain; If you need help with emergency-backup pm me, please. >> > I haven't used Kali, but make sure you're trying to decrypt the right device. It's actually a partition on the SSD you want to mount and decrypt, not the entire SSD device. -- - don't top post Mailing list etiquette: - trim quoted reply to only relevant portions - when possible, copy and paste text instead of screenshots -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/7f480901-d8a4-b4c1-d47e-e1713c951dd3%40danwin1210.me.
[qubes-users] Post Fedora-32 Template Installation
I installed a clean Fedora-32 template today, but I have some issues and I am not sure where to start. After installing the F-32 template I switched the default-mgmt-dvm qube to use the F-32 template. I then created a new qube basing it on the F-32 template, test-fedora-32-template, just to check that everything is working ok on this test vm before changing all of my F-31 based qubes over to F-32. I am unable to boot the test-fedora-32-template qube. After a while I receive a system notification, the ones that pop up top right of the screen, saying, 'Cannot connect to qrexec agent for 60 seconds, see /var/log/xen/console/guest-test-fedora-32-template.log for details' and if I look in the log file I see hundreds of messages like this... '.Failed to fork() worker: Cannot allocate memory' '.systemd-udevd[272]: xvdc1: Failed to process device, ignoring: No space left on device' '.eth0: Failed to process device, ignoring: No space left on device' The F-32 template itself starts up without any problems. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/6875558c-78b0-fc64-699b-979ea462f7c1%40ak47.co.za.
[qubes-users] pen testing / port forwarding guide?
hi, Has anyone written a guide to setting up a Kali vm in Qubes for pen testing? I'm studying for the OSCP, and the Qubes firewall port forwarding guide suggests a fragile and finicky setup that I'm reluctant to rely on. Punching holes from sys-net to sys-firewall to vpn-vm to an an appvm just to run `nc -nlvp ` seems... like a kludge, at best. Issue #4028 tracks this problem. The alternatives seem to be 1) create a HVM with direct access to hardware--no sys-net or firewall-vm--or 2) purchase a dedicated laptop for this use case. Any suggestions? thanks, jmp -- J.M. Porup www.JMPorup.com -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20200714155430.GA1026%40disp7009.
[qubes-users] Re: DisposableVM Help
Thank you both. For security reasons, in case the DVMTemplate has been compromised, I deleted it. How would I go about properly creating a fedora-32-dvm with the 'template_for_dvms' flag set? Thank you -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/6d86fa1d-ba2a-413f-be76-c027baf82a3co%40googlegroups.com.
[qubes-users] Re: Using Zoom in Qubes
Cool. Even better! Works! On Tuesday, July 14, 2020 at 2:30:43 PM UTC+2, GWeck wrote: > > There is a somewhat lengthy discussion in > https://github.com/QubesOS/qubes-issues/issues/5863. > > For me, setting > > showframewindow=false > in ~/snap/zoom-client/current/.config/zoomus.conf worked. > > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/ea351b8b-7e46-48b8-8fc1-155e60a8d6afo%40googlegroups.com.
[qubes-users] Re: Using Zoom in Qubes
There is a somewhat lengthy discussion in https://github.com/QubesOS/qubes-issues/issues/5863. For me, setting showframewindow=false in ~/snap/zoom-client/current/.config/zoomus.conf worked. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/b7e1f8eb-7574-4bd0-befe-f7320f947f5eo%40googlegroups.com.
[qubes-users] Re: Using Zoom in Qubes
Oh. it works now! I needed to share first, and then do the xdotool trick... On Tuesday, July 14, 2020 at 2:12:23 PM UTC+2, peter@gmail.com wrote: > > > > On Sunday, May 10, 2020 at 8:00:57 PM UTC+2, Vít Šesták wrote: >> >> The problem with Zoom is probably that it opens a transparent overlay, >> likely because of annotations. However, Qubes OS does not support >> transparency. There is a workaround that hides the overlay: >> >> xdotool selectwindow windowunmap >> >> Regards, >> Vít Šesták 'v6ak' > > > Neither 'xdotool selectwindow windowunmap' nor ' xprop -f WM_STATE 32c > -set WM_STATE 1' worked for zoom in my case. > How can i share a screen/window with zoom? > > Thanks > > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/35cc102b-5b6d-4539-882c-654a6f9cccbco%40googlegroups.com.
[qubes-users] Re: Using Zoom in Qubes
On Sunday, May 10, 2020 at 8:00:57 PM UTC+2, Vít Šesták wrote: > > The problem with Zoom is probably that it opens a transparent overlay, > likely because of annotations. However, Qubes OS does not support > transparency. There is a workaround that hides the overlay: > > xdotool selectwindow windowunmap > > Regards, > Vít Šesták 'v6ak' Neither 'xdotool selectwindow windowunmap' nor ' xprop -f WM_STATE 32c -set WM_STATE 1' worked for zoom in my case. How can i share a screen/window with zoom? Thanks -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/03a283a9-242a-40aa-a9df-2095b0df80f3o%40googlegroups.com.
Re: [qubes-users] Fetching updates after disabling qubes-update-check in clearnet qubes
> <<--snip-->> Though it's not clear to me whether this is actually an issue, I figured I'd do it anyways. My question is, if I wanted to disable qubes-update-check service, how would I go about updating my templates over tor? Do I create debian and fedora templates linked to sys-whonix just to get updates? AFAIK the updates themselves run over sys-whonix by default. So, if you run e.g. "apt-get update" on your debian-10 template, this connection goes over tor. However, the notification about updates to run (yellow update wheel widget in the right top corner) goes by standard over the AppVM and so, most of the time over the clear (as your clock, that updates over sys-net). Since user-action is required (by running the update widget, or, as me, doing it all by hand), the notification is rather uncorrelated to the download action, I second Marek here. It is, as always, a convenience-vs-security question. You may uninstall the qubes-update-check service and run (checks for) updates by hand (or script) periodically in your template-VMs. The gain is small, the pain is high, so most people don't do it. That is my pov, maybe there is some contradicting one? -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/7ab1b814-fbc3-7828-7fe5-b7e9505e0fad%40web.de.
