Re: [qubes-users] Re: QSB #050: Reinstalling a TemplateVM does not reset the private volume
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 25/07/2019 8.21 PM, Andrew David Wong wrote: > On 25/07/2019 3.27 AM, Claudio Chinicz wrote: >> Hi Andrew, > >> I needed to reinstall Whonix-gw after having removed all >> templates. I've followed the instructions contained below on >> "Workaround" >> https://www.qubes-os.org/doc/reinstall-template/#manual-method >> and issued command "sudo qubes-dom0-update >> --enablerepo=qubes-templates-community qubes-template-whonix-gw" >> on dom0. > >> I've got a message "Using as UpdateVM to >> download updates for Dom0; this may take some time" but after >> many hours nothing happened. > >> Did I miss something? > >> Thanks > > > If you're downloading over a slow connection or over Tor > (sys-whonix), it could take a very, very long time, depending on > the speed of the circuits you're using. > > Also, are you sure that "qubes-template-whonix-gw" is the correct > package name and that there shouldn't be a version number (e.g., > 15)? > Since you specifically want to reinstall Whonix (or at least whonix-gw), it might be a better idea to remove the desired TemplateVM(s), then follow the Whonix documentation to install them again: https://www.whonix.org/wiki/Qubes/Install - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAl06VnoACgkQ203TvDlQ MDCgKA//Z8Javw+f/OiDwpyJP09SdIEe7lnf35XUvRu5oNmmO/+FQTfGwPLyfcil yOmlD2PiZeH7RguCB98P7RvioWibA/R2vdacMS289N7j0y9b46FJdqpEHLfIVJWP 3qRW6yW7Sy6EnFiEqpbic7gqSIxDJanQMsw3Wn0QlJYs3VbIm3Z9FYkzGbHE8LQh wAvKKmpdDjCBfc8S2mwYkeROYmy51tA/+MevZhFq7uzRh/hHiKxXuhbSaAY+y4r5 /RQJ/qsUyRUeaXhJ8qSqIrUbFLLtNVxd/oY79vTKz4+UthMMPWOv5KRKQaY460Fi v35C71tUqkrwMB42VjnvPeODhq5GmUpVAoT22qMqkSclgfcbadFGQhhw0rsAXYp3 CBBVgGkzbchUCTo7ryO2NKeZzWIX0OeVkIAJ+G+YkOg3jYDQCBjMXhc43aw6WYk8 Zv4RqlxvWRxXE5LF1Jy5yIT0GCqM2F3e1DNvagAihr8VqbviZYo/i7izbilNxgyQ RMW8ZFvqfh/hYZJTiycWn3oVe5+f/+CNJg6kY2MFOGj/IbpOkzrdMAcRPfrhm32S HkAcSVrp/DDRI5fISxt80cCWvKNPGLqJrVWdKJriXKrBpCGrZnEMtGjrUUDBL6r/ vknmLV/n1c5PCKSgqejzJYGBTx+U0m0C7uXU42WMBkJGo0BYsTs= =sK+0 -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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/5215701b-c229-9b68-0f77-3142744cd358%40qubes-os.org.
Re: [qubes-users] Re: QSB #050: Reinstalling a TemplateVM does not reset the private volume
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 25/07/2019 3.27 AM, Claudio Chinicz wrote: > Hi Andrew, > > I needed to reinstall Whonix-gw after having removed all templates. > I've followed the instructions contained below on "Workaround" > https://www.qubes-os.org/doc/reinstall-template/#manual-method and > issued command "sudo qubes-dom0-update > --enablerepo=qubes-templates-community qubes-template-whonix-gw" on > dom0. > > I've got a message "Using as UpdateVM to download > updates for Dom0; this may take some time" but after many hours > nothing happened. > > Did I miss something? > > Thanks > If you're downloading over a slow connection or over Tor (sys-whonix), it could take a very, very long time, depending on the speed of the circuits you're using. Also, are you sure that "qubes-template-whonix-gw" is the correct package name and that there shouldn't be a version number (e.g., 15)? - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAl06VZIACgkQ203TvDlQ MDCY7A//bP5RkJ7J3QiQ31jHRcmMFQ6HnIJgj3eixfAhvcQhzwM8jF6vL8wsKVo1 2toSnOOrmCxSnf4uSgScXzQCOe7fE0p02Qv3VanrbauKF6t7yA89nqbNVjg8Lj4c B+wt2n3Xubq5jmBJP2JFzh/FAQlt98iDuckV65Sud2CkrAPcTgu+7GDyCh3p5VDp ySHCrjVRXWXeURihq1jmJOjRPcPVH2bYbMxDy16FuUX/HLNp5DXFtL2EWFNk+e2U AuZVwPCW/WW3WPRTddvwakYMz/8/cEl9mnlrAmuZeKPCKpvJmVtEBVVHPkoJ7S2T AwZ7afje6Kb8S5l2vo7CNxHN0MkVBkWHGEFKoA5RrJvEwWf4yCf6kyFE7AEMDEoj u6lgWcXZOzlj0lbpT8zeIrkecZ6Xol9enqITUXfmSGL3LRGMaSzy7J7Iu+q1ZIAW RuRIpZlgSg/99kVEmT9480kA84TxoUs+xfoV6/3qmQ7jlYV64gQwtvPds2fk8t2Q oxPDKxrpIYGCMB9m3t4GRBkG4WLJyz3p47HuJ68ht7EcwrNfX9p3TmK7VjAcl8WH A8EgiiglFuz58zk1hUWl2VWVRLtvKg/jzR4d/xV9KR5/vgyX/oEQ+F+WeV7dFMRa RwIKlFM+xFsE0AWFfzm39J0/cRrRJ5GTVF4dkc3GCm26aYY4gj4= =OYnS -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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/b2a70d2c-d9f6-157e-a302-3c435c4930e3%40qubes-os.org.
Re: [qubes-users] Re: Confuse Update QUbes OS
On Thu, Jul 25, 2019 at 02:11:40PM -0500, Sven Semmler wrote: > On 7/25/19 10:48 AM, unman wrote: > > Debian-10 is stuck in testing at the moment because it needs packages > > from the *testing* repositories for updating. This could be confusing if > > users install from current and don't want to use the testing > > repositories. > > I'm sorry that confused me. My main template is buster based and pulls > from "/r4.0/vm buster main". Everything looks fine. Can you please > clarify what you mean with the above? > > /Sven > Qubes packages - require =versions only in testing. Try to install some new packages. Most evident when using 10-minimal -- 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/20190726002627.hmslcnpfi6vcccsc%40thirdeyesecurity.org.
Re: [qubes-users] Re: Confuse Update QUbes OS
On 7/25/19 10:48 AM, unman wrote: > Debian-10 is stuck in testing at the moment because it needs packages > from the *testing* repositories for updating. This could be confusing if > users install from current and don't want to use the testing > repositories. I'm sorry that confused me. My main template is buster based and pulls from "/r4.0/vm buster main". Everything looks fine. Can you please clarify what you mean with the above? /Sven -- 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/09a85f7f-4203-9258-9f90-2a7c43c1fa88%40SvenSemmler.org. signature.asc Description: OpenPGP digital signature
Re: [qubes-users] R4 system requirements; AMD compatibility?
On Thu, Jul 25, 2019 at 12:15 PM Chris Laprise wrote: > If it doesn't work, then the problem is probably entirely in dom0 and > Fedora 25. Assuming you already have the testing 4.19 kernel, have you > thought of upgrading it to the even newer 5.x one as 'latest'? The > latest kernel is installed by specifying the special package named > 'kernel-latest'. qubes-dom0-update kernel-latest # will update available dom0 kernels list and sets most recent as default qubes-dom0-update kernel-latest-qubes-vm # will update available VM kernels list and requires manual checking to see if it changed your global defaults and/or changed a per-VM kernel setting when older ones are removed I use both and generally pull from current + current-testing repos. Currently running 5.1.17-1 in dom0 and a mix in VMs under R4.01. B -- 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/CAOajFeeHFK_kngBYcPou%2BQLeqrg1Ef92j05_s7%3DGDUYXAE0iPw%40mail.gmail.com.
Re: [qubes-users] R4 system requirements; AMD compatibility?
On 7/25/19 11:04 AM, brendan.h...@gmail.com wrote: ...there are very very early test-builds of Qubes R4.1 out there utilizing Xen 4.12 and Fedora 30. This 2019-07-01 build appears semi-stable in light testing. It is, at a high level (and Marek can correct me if I am wrong), the R4.01 codebase with up-to-date Xen and dom0 Fedora w/ any Qubes-related changes to ensure these work with the Qubes code base. I was able to install that particular test build on a Thinkpad X230 for testing: https://openqa.qubes-os.org/tests/3021 (note: click on assets tab for link to download the ISO) It might be worth installing one of those as well on another drive to see if newer Xen/Fedora combinations resolve sleep issues or get you closer to resolution. Interesting link! I was just thinking this could be an "old Fedora" problem. But that also suggests there may be a way to patch the current dom0 to handle suspend correctly. Of course, domU is a factor if sys-net or sys-usb are running. Claudia: Have you tried suspend/resume with no VMs running at all? This can be accomplished by manually shutting down appVMs then service VMs, or with the command 'qvm-shutdown --all --force --wait'. If this works, then the problem may be in the VMs such as sys-net or sys-usb. This is possible because those VMs control hardware that must also respond to special commands related to sleep/wake. If it doesn't work, then the problem is probably entirely in dom0 and Fedora 25. Assuming you already have the testing 4.19 kernel, have you thought of upgrading it to the even newer 5.x one as 'latest'? The latest kernel is installed by specifying the special package named 'kernel-latest'. -- Chris Laprise, tas...@posteo.net https://github.com/tasket https://twitter.com/ttaskett PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 -- 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/02f1d4e0-f84c-d4b8-1f27-9924ab5a30bc%40posteo.net.
Re: [qubes-users] Re: Confuse Update QUbes OS
On Thu, Jul 25, 2019 at 08:49:00AM +, 'awokd' via qubes-users wrote: > Jon deps: > > > if the debian 10 sentence is current, is the documentation soon to be > > updated ? > > > > any guesstimate on the -10 fresh templates ETA <-- sorry to ask?? :) > > The Debian 10 Qubes template isn't out yet. It's in testing so it should > be soon. Hopefully, associated documentation would be updated around the > same time. > > > PS: in tbird how does one reply to > > awokd > > > > I can a popup error recipient name rejected no domain found > > > I don't know how Gmane works. Maybe you can't reply to posters directly > with it. Using the Qubes listserv with email does work for that. > Debian-10 is stuck in testing at the moment because it needs packages from the *testing* repositories for updating. This could be confusing if users install from current and don't want to use the testing repositories. Also, I've noticed a few regressions in the minimal template which need fixing before release. So testing it remains. Andrew will announce when the templates become available in "current". I don't think that Gmane works any more, does it? If you have a message referenced ed there you should be able to find it in archive.org, and reply from there. -- 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/20190725154830.vwiguyzolb4myxyf%40thirdeyesecurity.org.
[qubes-users] Dual-booting Windows vs HVM
What is the best option for using Qubes alongside gaming on Windows? I am currently dual-booting without Anti-Evil-Maid, reason being that my Intel ME is disabled with me_cleaner. The OS is locked down and I don't update my Windows at all to prevent further spying features being added/reenabled. Using the IGPU and passing it -- 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/-qvh7yzAuzSaFf-AHu0v9CaNzNiYo8zrEqk3HaH3d3RXalSTzURlc4259nViY0ZTJsXh3xGb1x5cvlLlT8bXtDb1eOhdeBIwGoeCtNX_DBY%3D%40protonmail.com.
Re: [qubes-users] R4 system requirements; AMD compatibility?
On Thursday, July 25, 2019 at 10:18:29 AM UTC-4, awokd wrote: > > > Are there any other Xen-based distros out there I could test? > > You can add Xen to your stock Fedora install. That takes it roughly to > where Qubes begins, but you might want to use the same version of Fedora > dom0 uses. > > Claudia: I'm sure the *last* thing you want to do is add additional variables, as things are easier to diagnose with fewer, but... ...there are very very early test-builds of Qubes R4.1 out there utilizing Xen 4.12 and Fedora 30. This 2019-07-01 build appears semi-stable in light testing. It is, at a high level (and Marek can correct me if I am wrong), the R4.01 codebase with up-to-date Xen and dom0 Fedora w/ any Qubes-related changes to ensure these work with the Qubes code base. I was able to install that particular test build on a Thinkpad X230 for testing: https://openqa.qubes-os.org/tests/3021 (note: click on assets tab for link to download the ISO) It might be worth installing one of those as well on another drive to see if newer Xen/Fedora combinations resolve sleep issues or get you closer to resolution. Brendan -- 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/141ed585-2869-485b-9716-33bb5b2a1c16%40googlegroups.com.
[qubes-users] Re: Changing the clipboard shortcut in 4.0 doesn't work
As a follow-up because I see this has been asked at-length both here an on GitHub: I tried changing this to "Ctrl-Alt-c" and "Ctrl-Alt-v" in /etc/qubes/guid.conf (using that syntax and capitalization EXACTLY). Is my syntax incorrect? I had this working in 3.2, but it won't work in 4.0. Strange . . . On Wednesday, July 24, 2019 at 7:33:10 PM UTC-5, arthur...@gmail.com wrote: > > I prefer to use a different shortcut for the Qubes clipboard because > Ctrl+Shift+V is an existing shortcut for "paste without formatting" in most > applications. However, I've tried editing /etc/qubes/guid.conf and > restarting my VMs (I actually restarted my whole system), but no luck. I > figure something changed now that the clipboard is a standalone > application, but I'm not sure what needs to be modified. > > 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/2bee2e3f-a669-4949-9950-2e34c19b2584%40googlegroups.com.
Re: [qubes-users] R4 system requirements; AMD compatibility?
Claudia: > This also really complicates the search process. It's not good enough to > find a laptop that is known to suspend under Linux. It's a wonder > *anyone* has working suspend in Qubes. Unfortunately, this is true! Lots of things have to work together in order for suspend to function. See https://www.mail-archive.com/qubes-users@googlegroups.com/msg27682.html for an example with my AMD laptop. > Are there any other Xen-based distros out there I could test? You can add Xen to your stock Fedora install. That takes it roughly to where Qubes begins, but you might want to use the same version of Fedora dom0 uses. -- 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/7bca61a9-e73b-5970-ef5a-43530343f602%40danwin1210.me.
Re: [qubes-users] R4 system requirements; AMD compatibility?
Chris Laprise: My experience is that consumer BIOS will result in poor suspend compatibility. Not surprising :( But there are indeed some Thinkpads, MSI, System76, Purism, and other high-end business-class machines on the HCL with suspend not working. So it's still a bit of crapshoot. Just don't want anyone thinking they're "safe" if they buy an expensive machine. You should try these: * Find which wifi modules are being used in sys-net (i.e. do "sudo lsmod") then add them to /rw/config/suspend-module-blacklist. I find this is usually required to get suspend working right. For an Intel wifi card, you would add both 'iwldvm' and 'iwlwifi' in that order. I did that for ath, ath10k_pci, and ath10k_core in sys-usb. No dice. Would it help at all to try blacklisting them from dom0, just for testing purposes? Also: order matters? * Upgrade the dom0 and vm kernels to 4.19 or later. The 4.19 versions from qubes*testing have been very stable for me. OTOH, there are also 5.x versions available. Upgraded to latest dom0-current-unstable, 4.19.something. Only thing this changed was that the boot process hangs between Xen and dom0 kernel about 50% of the time. Tried this and the above fix together. Where can I get these 5.x versions? --- I also was able to upgrade the BIOS to 1.3.2 using Freedos. No dice. BUT! I made a small breakthrough. It suspends and resumes flawlessly under Ubuntu and Fedora. This stands to reason, as according to Dell the machine officially supports Ubuntu. So it appears nothing is fundamentally broken here. I did some testing to try and narrow it down and here's what I found so far: Qubes R4 with 4.14 & 4.19 - doesn't work Ubuntu 19.04 with 5.0.0 - works Fedora 30 with 5.0.9 - works Fedora 29 with 4.18.16 - works Initially I was hoping the fix is already in ~5.0 mainline. But isn't the Qubes kernel based directly on the Fedora kernel? Why would it be working on an *older* Fedora kernel and not on a *newer* Qubes unstable kernel? So what's the outlier here? Xen? IOMMU? XFCE? (test systems were all GNOME) This part is interesting. I tried disabling VT-x and VT-d in BIOS and booting Qubes. It suspends as usual, except now, when I hit a key to resume it, the fan comes on (unlike before), and it sort of sounds like the disk spins up, but the display doesn't power back on. Also, the light on the caps lock key doesn't come on when I press it, and Alt-SysRq-B doesn't do anything in this state, even after enabling it beforehand. In other words it feels like it's trying, but won't fully resume. So I guess this tells me that it's partly virtualization related (because it behaves slightly differently when virtualization is disabled) and partly not (because it behaves differently under Qubes with virtualization disabled than it does under Fedora). Maybe it's a Xen issue, regardless of virtualization enabled/disabled? This also really complicates the search process. It's not good enough to find a laptop that is known to suspend under Linux. It's a wonder *anyone* has working suspend in Qubes. Note I'm assuming it's a kernel-related issue, but I guess it could be something else entirely -- power management utility, udev, xfce, who knows what. Point is, if it's just a version issue, I can deal without suspend for a while until the fix makes it to Qubes. But if it's some deeply-rooted virtualization issue, I sort of doubt it'll ever be fixed, whether in kernel or in BIOS. Are there any other Xen-based distros out there I could test? I know it's a lot of guesswork, but I value your advice. - This free account was provided by VFEmail.net - report spam to ab...@vfemail.net ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the NSA's hands! $24.95 ONETIME Lifetime accounts with Privacy Features! 15GB disk! No bandwidth quotas! Commercial and Bulk Mail Options! -- 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/0379edd3-ebbe-ef01-27f3-42ff066f50ab%40vfemail.net.
Re: [qubes-users] usb modem via PCIe installation issue
alain.cor...@gmail.com: > Hi, > I need to use a telit lte modem plugged on PCIe. > I found informations > dmesg: usb 1-2: product Telit... > lsusb: bus 001 Device 002: ID Telit .. > readlink: /sys/bus/usb/devices/usb1 >..device/pci.00:14.0/usb1 > it's ok, but... > when i attach the usb device from dom0 > qvm-device pci attach myVm dom0:00_14.0 > > Qubes-Os stops. > I don't have no more acces at nothing. > keyboard, mouse which are usb devices are lost. > I have to unplugge the supply to reboot. > has somebody a solution? > Thanks > alain > Since it shows up as a USB device, try attaching it with the appropriate qvm-usb commands instead. Also, you should almost never attach devices to dom0. Attach to a qube instead, such as sys-net. -- 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/5939f669-2e4a-24f1-c415-ff427511a474%40danwin1210.me.
[qubes-users] usb modem via PCIe installation issue
Hi, I need to use a telit lte modem plugged on PCIe. I found informations dmesg: usb 1-2: product Telit... lsusb: bus 001 Device 002: ID Telit .. readlink: /sys/bus/usb/devices/usb1 ..device/pci.00:14.0/usb1 it's ok, but... when i attach the usb device from dom0 qvm-device pci attach myVm dom0:00_14.0 Qubes-Os stops. I don't have no more acces at nothing. keyboard, mouse which are usb devices are lost. I have to unplugge the supply to reboot. has somebody a solution? Thanks alain -- 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/6af3e349-8ab8-40df-ba98-80f05512c7d7%40googlegroups.com.
Re: [qubes-users] Re: Confuse Update QUbes OS
Jon deps: > if the debian 10 sentence is current, is the documentation soon to be > updated ? > > any guesstimate on the -10 fresh templates ETA <-- sorry to ask :) The Debian 10 Qubes template isn't out yet. It's in testing so it should be soon. Hopefully, associated documentation would be updated around the same time. > PS: in tbird how does one reply to > awokd > > I can a popup error recipient name rejected no domain found > I don't know how Gmane works. Maybe you can't reply to posters directly with it. Using the Qubes listserv with email does work for that. -- 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/c81fd577-9bbb-6d7a-9fb8-da8cfd45aeab%40danwin1210.me.
[qubes-users] Re: QSB #050: Reinstalling a TemplateVM does not reset the private volume
Hi Andrew, I needed to reinstall Whonix-gw after having removed all templates. I've followed the instructions contained below on "Workaround" https://www.qubes-os.org/doc/reinstall-template/#manual-method and issued command "sudo qubes-dom0-update --enablerepo=qubes-templates-community qubes-template-whonix-gw" on dom0. I've got a message "Using as UpdateVM to download updates for Dom0; this may take some time" but after many hours nothing happened. Did I miss something? Thanks On Thursday, 25 July 2019 07:14:34 UTC+3, Andrew David Wong wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > Dear Qubes Community, > > We have just published Qubes Security Bulletin (QSB) #050: Reinstalling > a TemplateVM does not reset the private volume. The text of this QSB is > reproduced below. This QSB and its accompanying signatures will always > be available in the Qubes Security Pack (qubes-secpack). > > View QSB #050 in the qubes-secpack: > > https://github.com/QubesOS/qubes-secpack/blob/master/QSBs/qsb-050-2019.txt > > Learn about the qubes-secpack, including how to obtain, verify, and read > it: > > https://www.qubes-os.org/security/pack/ > > View all past QSBs: > > https://www.qubes-os.org/security/bulletins/ > > ``` > > > ---===[ Qubes Security Bulletin #50 ]===--- > > 2019-07-24 > > > Reinstalling a TemplateVM does not reset the private volume > > Description > === > > In Qubes OS, we have the ability to reinstall a TemplateVM by running > `qubes-dom0-update --action=reinstall qubes-template-...` in dom0. [1] > This is supposed to reset the corresponding TemplateVM to the state of > the published package, i.e., no local changes should remain. > > One uncommon reason to perform such a reinstallation is that you suspect > that a TemplateVM may be compromised. In such cases, it is very > important that no local changes persist in order to ensure that the > TemplateVM is no longer compromised. > > Due to a regression in R4.0 [2], however, reinstalling a TemplateVM > using qubes-dom0-update does not completely reset all local changes to > that TemplateVM. Although the tool itself and our documentation claim > that the private volume of the TemplateVM is reset during > reinstallation, the private volume does not actually get reset. This > could allow a TemplateVM to remain compromised across a reinstallation > of that TemplateVM using qubes-dom0-update. > > Workaround > == > > Fixed packages are forthcoming. In the meantime, we recommend avoiding > the qubes-dom0-update method of reinstalling a TemplateVM. Instead, we > recommend manually removing the TemplateVM, then installing it again. > Detailed instructions for this manual method are documented here: > > https://www.qubes-os.org/doc/reinstall-template/#manual-method > > (Note that we have updated this page with a warning against the > automatic method.) > > Patching > = > > We expect to have fixed packages available next week. In the meantime, > please follow the workaround described in the previous section. We will > update this QSB when fixed packages are available. > > Credits > > > Thank you to Andrey Bienkowski > for > discovering and reporting this issue. > > References > === > > [1] https://www.qubes-os.org/doc/reinstall-template/ > [2] > https://github.com/QubesOS/qubes-core-admin-linux/commit/552fd062ea2bb6c2d05faa1e64e172503cacbdbf#diff-6b87ee5cdb9e63b703415a14e5a505cdL192 > > > - -- > The Qubes Security Team > https://www.qubes-os.org/security/ > > ``` > > This announcement is also available on the Qubes website: > https://www.qubes-os.org/news/2019/07/24/qsb-050/ > > - -- > Andrew David Wong (Axon) > Community Manager, Qubes OS > https://www.qubes-os.org > > -BEGIN PGP SIGNATURE- > > iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAl05LEEACgkQ203TvDlQ > MDCA2Q//SBZ/v5eDrOauzdvQcqpgDJHGZyT34b1POcu8u4iAFWXBrnBSYgefDN0d > uMoxcZOy+q+GCy9r176MWl17m1td3ev/WnSgCwcUnDvegC2jLacixqMuoVxXDW3A > 6Mvu/Ui73O7bh3fAemoRHP7ts4ZKCZ9LGWEcIzlzR+Sg6jYDLC2sg3xRhp+G1GLX > Jduisn0ZnsTOGAgPnt0MZarn2MXoQt6A+6IwbN5g48Y/2anjiwz45Etkl9y2XTQZ > kfWelmuraf+adKrbqEjYEapl6ARuPsuoR1rb3sSEqVApHZY1syfAioLNHbOfRrmW > oqNPK/GnkOo7wWXyymZPQDDXor6GojYrLbocUcI+KcObiFnGEeqzzRp+s9lm641t > cXHdk+309U1H+z7DRKWeeGW2UZ39hof14bxemWqQnIaLYn0flOX15ke8DANDh9dF > 7BRDyTuoFBqOy3W8Ab1iJoVi5ZhyNDOOmzXzkvqyP0lzAtX2AtJlXWUGMIAo+Pqp > z6JH3qXbpBZgJb71qIOU85Eb9FfYgseQa9y2msswiGCh/xpv+/il7WP577/w/FKr > GzV/h2Bw/QTcFj+nLMCnCVF0RZ8XwZ9wz6p/Qy4DxYseNyV0C4efv0zrErzX9a4x > /Ug8jcexTq96sawNTCLVIiIIdAtsIy3y7NCDQtjswiIxVCZKMcQ= > =5Wik > -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 view this discussion
[qubes-users] Re: Confuse Update QUbes OS
On 7/19/19 9:11 PM, 'awokd' via qubes-users wrote: Luc libaweb: Hello, When I update my Dom0, I have : Failed to synchronize cach for repo "template" and "current" But, I have then nothing to do and complete. This error is usually temporary, like if you are having internet trouble. Try running update again. Qubes OS is updated ? My release cat is 4.0 but not 4.0.1 ? A fully patched install of 4.0 is no different than 4.0.1. I don't uderstand if I have to upgrade template or it's automatic whith the update tool. Thanks The update tool will update patches within templates. However, it does not handle updating to entirely new template versions like Fedora 29 to 30 or Debian 9 to 10. See https://www.qubes-os.org/doc/templates for those. if the debian 10 sentence is current, is the documentation soon to be updated ? any guesstimate on the -10 fresh templates ETA <-- sorry to ask :) PS: in tbird how does one reply to awokd I can a popup error recipient name rejected no domain found -- 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/577a44a3-ae99-7b8e-64b3-c2482cb33cb4%40riseup.net.
