Re: [qubes-users] Using sys-whonix with Windows AppVM
Am Donnerstag, 30. Mai 2019 18:19:17 UTC+2 schrieb 0brand: > Hi Roger, > > > > > Did anybody connect a Win AppVM to sys-whonix? Any additionnal steps that > > have to be taken? > > Its difficult to tell what the problem is without system logs and/or > error messages. > > You can take a look at the Whonix docs. (it is possible to do this). > > https://whonix.org/wiki/Other_Operating_Systems#Windows-Whonix-Workstation_.E2.84.A2 > > Regards > > 0brand > > -- > GPG Public Key: 0x09B31BA99EC051FE > Fingerprint: 4452 4D54 4EB2 53E8 1EE9 223A 09B3 1BA9 9EC0 51FE Thank you. There it says you should be able (for the least secure method) to hook sys-whonix to the Windows VM and this it. When I connect sys-net, it works. When I create a VPN VM and connect it, it won't work neither.. All of them work with the Personal Domain, unfortunately not with the Windows machine. :( -- 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/7fd319f8-c0ca-4586-b61f-2abbf6ccd57c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] dom0 kernel 4.19.43-1 update a fix for ATI Radeon cards, or the original?
On Thursday, May 30, 2019 at 4:19:10 PM UTC-7, awokd wrote: > drok...@gmail.com wrote on 5/29/19 3:09 PM: > > On Saturday morning, dom0 had a kernel update 4.19.43-1 which broke Qubes > > for people with older ATI Radeon cards. It was temporarily pulled. > > > > I see the same kernel is now back in the updates repository. Is this the > > same kernel which breaks ATI Radeon cards? Or is it a different kernel, > > that fixes the ATI Radeon breaking issue. > > > > I am afraid to install the update. If it is the same kernel (it is same > > number) it will break my Qubes install again. I am not looking forward to > > going thru all of that again. I checked on the open issues page, and > > didn't see any info on this update, one way or the other. If I missed it, > > I apologize. I'm fairly new to Qubes and still learning how support works. > > Are you sure it's not 4.19.46-3 (the fixed version)? I found the page that shows you and others working on it: https://github.com/QubesOS/qubes-issues/issues/4934 If I recall correctly, that fixed version is pushed to testing. The update I saw in stable is gone again, and I'm running the current 4.14.119-2 for dom0. Everything is working now. Thanks for following up :) -- 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/cb80c263-91cf-420e-bb82-44b7cc85a6e5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] qubes-networkmanager
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 30/05/2019 9.23 PM, haaber wrote: > As you can easily see, the access credentials (passwords) for wifi > networks are stored cleartext in /etc/NetworkManager of sys-net. On > the other hand side, this VM is a "dangerous" place to store > passwords in. Wouldn't it be natural (maybe I ignore that this > already exists) to store them rather in vault and to have a > "split-nm" similar to solutions as split-pgp or split-ssh ? > Cheers, Bernhard > This topic was previously discussed in this thread: https://groups.google.com/d/topic/qubes-users/DlCcShB-kbU/discussion - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlzwkhEACgkQ203TvDlQ MDAywBAAjeXrdR2cItYI8JRQtI/7Da8LQiQScLidCJqzzo/yNukiZrJ0l5idNy9A /2hwu1Xq4qm3DbBrDhGynTFfXXGbkMuJtHpXz+uZDVqCKzeF9HFb18TvlJ18EmTl sIJZHHkTQHp0DSSOUkdSuCOrFqhfZqvv5JhEkkezhonib5y7F7Dy1aWFllwBN0iC 6dQxJKuQ9Ur9hGC3OReO+pe6H540/hlOQteIJqgHdbWRvAxq7s0Y6eNxc03gbPh0 Hldzcsojg1hjy6d4r4c5gYNDxR1U3eAzukKC5lncr20NJuxNzGnjEy2CrHmyTYxm aAGMMDjSsyBs2ZZea9+A785waR+yNt5C/J06y16sOGeAdPtjiX7hFoTZTdfAJV5u q4mTRwlBtlrYnHSTjmbJxRk0aWg42CYUWHDVvioTv0MPGLOtZWe6TkZEZ7t0tv4f LDkzwcUPGMy3DM8iz6yBbvcH3ELF69lhfOvO956yYrRqaql+LE5WL0+kvtEhJGnE 6sMLepsV8BoLHqHwb9Jf3Wa1/1cMh4tFheRLhJCfSTWOdvJx9mMyZpkwD9uJzVNO RcF1HoqPn5c+TPsa7muLvWKFD1qt0+i/80r1SuhoeuHVRLO/hfM/DzkE7nSmz6dh 10UIMBJB2OxTgddi81Nm/vESSn1U5zez0uF/YRG5viCUUHGmQA8= =Wc7p -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/5cecb451-4b35-bac4-bbf5-6433443c72f4%40qubes-os.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] qubes-networkmanager
As you can easily see, the access credentials (passwords) for wifi networks are stored cleartext in /etc/NetworkManager of sys-net. On the other hand side, this VM is a "dangerous" place to store passwords in. Wouldn't it be natural (maybe I ignore that this already exists) to store them rather in vault and to have a "split-nm" similar to solutions as split-pgp or split-ssh ?Cheers, Bernhard -- 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/dd101e36-6cf4-cbb3-dda1-0518460ceebe%40web.de. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] No more updates for Fedora-29?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 30/05/2019 8.24 AM, Lorenzo Lamas wrote: >> The new Fedora 30 TemplateVM is currently in testing: >> >> https://github.com/QubesOS/qubes-issues/issues/4845 >> >> When it migrates to to stable, we will make an announcement, as >> usual. > > Actually, it is already in the stable repo: > https://ftp.qubes-os.org/repo/yum/r4.0/templates-itl/rpm/ > Thank you; I wasn't aware of that. I'll follow up on this on the issue. - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlzwj8cACgkQ203TvDlQ MDBc0BAAyTlpRKn269jtoPR7AH1pXWSmY32cViS8HZuJRE8V+/JAtEKLz5N9Ia9t WjbfqMIpIz56tcuj/j1eCw8j50Y2/HlzpzUjXmokybrKv1og/cr6y2YI3X0FPQ3A I+S1sBx/QXXPOXS0BuswXPRfI5fshyWxod0Yg1a+9GYvyyslb+Ayf+2mVDpFHHnh FQWZIDKIy1u1kSe49HOwiySMs5Li29Di3TYaA7tX6b8nTv3IkkMKvkg6qSyD9Fex Xoumn+a5Q9QV1ccTJN8jYvu5WIR5EgPt3fs7bm5paX5jE1QPKuBWdElSOTz5eP97 tsTk/f/ibcSoirAQXkyvn4VCl9vhb3f3avCJYxm7xVx4sRUcpQsdLvOtdMxPY37b 1JYht20LS1zHpbgyMOfpxhhHy6PQHkOw+ygHv9rvjejrxvFLvZDuWAGD6/QMXPsk BGw09jf/EZm1+BGIf5hscVMfqvBekxggtQEZymJvPZ+Q9JehLyz7cPSsIMWWVobo GUgr2wDHWTwuV0oEdc3cAM0SIZfwmEWT24uxvacddtB1jsGno9CvJ7M1MGOHRQZn xcvNdCA8s0uXDKaiGAks75yEcrAyP8sctEwSXgWvgwVZM9O6oz4y/VTYvbNECAh8 6rQM8rknxdhfRciK8c0q8VQ87ZheC8yKThaSlPpO4UD+jDRoZrE= =g6fS -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/9c8d3889-3327-0f20-b3ea-f0d4deb1ee43%40qubes-os.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Weird icon in Applications, behavior of the deleted VMs
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 30/05/2019 7.43 AM, scurge1tl wrote: > Yesterday I was experimenting with monero gui. I just unpacked the > monero-gui-linux-x64-v0.14.0.0.tar.bz2 (the hash and PGP verifications > were ok) in the AppVM named monero-on based on whonix-ws-14 and played > with it for some time. Than I deleted the AppVM and shut down the laptop > . > > Today, when I click on the Q icon Applications, I see a weird icon in > the list between domain: and service: named "monero-on-vm", with a > weird icon which looks like a box with trash or what. Options > available are: > > monero-on: Chat support > monero-on: Dolphin > > None is working when clicked. I thought the Q button Applications is > under control of dom0 and there is no way how the > monero-gui-linux-x64-v0.14.0.0.tar.bz2 would influence dom0 this way. > This usually indicates that the VM has been deleted, and the leftover Application Menu shortcut was not cleaned up correctly. It's a box of trash because the original, correct icon is no longer available. You can clean up the shortcuts manually using the information documented here: https://www.qubes-os.org/doc/managing-appvm-shortcuts/#behind-the-scenes > I don't know if it is related, but when booting to Qubes, and > watching the boot process, I can still see Qubes is trying to boot > AppVMs which are for months deleted, with "Failed to start" the VM. > How do I delete it permanently? > I haven't heard of this problem before. Please consider reporting this bug if it hasn't been reported yet: https://www.qubes-os.org/doc/reporting-bugs/ - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlzwj2kACgkQ203TvDlQ MDCcLA/+PDuzqqpl816BBd+pEjIAwKQiJbkSMd/snscb7D+EiITUymP4X/f7ZeRV Njh45jQRS9nJkQAwkOFvaV1Kp+tVHIsch6e8zDx80V3ycBOZdrm+0eICFAPDIHS7 GJ47gZsJMdTpLA592IAKqyONoFV8qr0IykADIqulAMoZu0We4Ro+jrx3JNsMF6XO Sp93sdMGu/wb+oIp3V9XKAPz/apSitUvryFi9cE/ZX72FHymHSbVMCj+HNaGlKFk GiBOeNUpz27mrf3O8bQ0LI6fVwMetCAmW9YfyoPCcC4EeguqMU8utvX2qxjSufnR 5RaF/COWhpR7dOn8QcFOFpM8TW3Qha88y5iOF8J7fg3Xxa73pc35O0lHBcd2Hhug JmvMeKa0uW63Eo9p749v18r1XfDaiSIsTtErHd/KwSAjXDAWkfiWbDKBwnzmi9I/ 70Rp1t7R7tVis9952d+sintROFOCSQ9/3H4IaiEr0odmWqIHHgt6qZpQdL/BLlAP UXYP9TLS9zkplLoV6d1csCa0RjVHxr+xBpvsOAG3iItx43hIu7m1UwJKS5SIg25y yNLbTL+SBAhXhQKX7ON9PdwI6Zu/T9AaBfPQX7v7OImRlwHz6CYCIR6C7Jk4CgHr taQaZD15B9q+DNOAPnBsHgQdv1W3xPC5LVJvc7rmuD1it69GLow= =rq7P -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/9d5b3eec-12b5-d27e-0079-629cad9e0c15%40qubes-os.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Global Setting return error
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 30/05/2019 6.25 PM, 'awokd' via qubes-users wrote: > scurge1tl wrote on 5/30/19 12:17 PM: > >> 'awokd' via qubes-users: >>> scurge1tl: The only thing I spotted to have issues, is the Global Settings button, which is not reacting. >>> >>> Check https://github.com/QubesOS/qubes-issues/issues/4988. Use >>> "qubes-prefs" in a dom0 terminal as a workaround. >>> >> >> Is there any guide of how to use the command? > > Most commands (including this one) in most distributions support > appending "--help" or prepending "man" to get more information. > Yes, it's always a good idea to use `man ` and `command --help` to learn more about how to use commands. The Qubes command-line tools are also documented here: https://www.qubes-os.org/doc/tools/ In particular, the qubes-prefs man page is available here: https://dev.qubes-os.org/projects/core-admin-client/en/latest/manpages/qubes-prefs.html - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlzwjgUACgkQ203TvDlQ MDDhXhAAuweYJpRQyEYCmGlol2mF5MxdvxQsRgxDcE/eN+Y0j6Wo0SbzDCQdIP25 hNTD3KodHrNcfNrHEGkh/wdgVDZ/WGrDrS/dtNeNzRs6XQkj1pANEAiT4bI9r1/2 VT5fYgBr0HAy5h+O8iEfhH/q7qF/2LwnOUBADjNRfcFxoIsdVDHDXsjVAJ7yPMOx pvK2aUQrFzvdesOwLm7SERJ6pUkOivDUDtWiWBCaXr86+tNLLF5+LBWTXF1YEoy7 8cjErAJNorRkxyyFaGnmYyen+CgMhJPe8Wq0WvpP6++0kOMJk19jAenTPjrg5yXW 2sSn+FD4mVK9XpAesSVvMi6tinzS6H9ubXQh/7mr0sgb/k4uR3ThaYGTbYzxujuV 9Qywyvcq7m6dOSdFn2YbQHJopm0ZSKxJizIUO50nybBieMaAxbjpKVJ4sogZeyFD nuFTJQ5avEgh1fjZN79cNlGlE1heQvtY/SJP8ig781QJkus/9eldkAeepRP8Vahi dS9F81rjV0sCH1J0fe87eYP+YOjoEnLBX6niFdXzfPTFY31QqPB/pdG8spp/hgCd X8AMiJ+eldjo4zxY5bqDTMhdCcAtt51p2BccyapwkLK+jz2vjfaH12SylNq0NEE2 7BcOeaaMhgBtp/dNXcqXFWHom8loNhPl5i53j9oWBCNinaIqkIg= =DQea -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/13444abf-28d9-fd75-cea7-278dd5f454cf%40qubes-os.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Fedora 28 has reached EOL
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 30/05/2019 6.46 PM, haaber wrote: > Just one question: which Fedora version is dom0 based on? In Qubes 4.0, dom0 is based on Fedora 25. This is always documented for every Qubes version here: https://www.qubes-os.org/doc/supported-versions/#dom0 > Is there some need for updates that I ignore? No. Dom0 is isolated from domUs. DomUs can access only a few interfaces, such as Xen, device backends (in the dom0 kernel and in other VMs, such as the NetVM), and Qubes tools (gui-daemon, qrexec-daemon, etc.). These components are security-critical, and we provide updates for all of them (when necessary), regardless of the support status of the base distribution. For this reason, we consider it safe to continue using a given base distribution in dom0 even after it has reached EOL (end-of-life). This is documented here: https://www.qubes-os.org/doc/supported-versions/#note-on-dom0-and-eol - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlzwjSMACgkQ203TvDlQ MDCaexAAi5PzP+sAwzFYhEydSXG5l5Wy+7HefNe41rdcSxl2D0YaBEiiGdKNw6ZN oMRpM3vODWuHV2bEBdkDktXRIuGdB82IKm0PqZn5gUfmUEGxfyL95oDl68qA50ZR X6fITb9lOZRj5eqbtC14TkEcEK4u1VerV5nC2Etm0nUfvXkT3gqc1yI8ZhSm+ZJz 4whaq8RHUDtoMYN7T9xIqh0VBWI8q5O3gHTGWFstT9BTJzRkiub/qsOVxrNAr6Ae ejTvE6NBSD9emtJWDEQeJscBiUOAFZbGjZaHoVyMZQaNy9wK3gruRY5W20arBJXL bD37p3lAdrloZsgYMUzv3ZQT0+HCY6v/Mll+/9HJuTP9yNK/0tsifK25x4iz45VN ncvPi1GPX4ixVlchdsdOCd7qz7ZtZ0+8X/YEY9LuvgK1eA8U4kpdUdm9qfPy6fUK kP610fUiEwzYq21a1DitpWsb5K8TlIbAhSYffIFsuIScAyrPq13FB/v2FNIRc54z uapogpUawFefxr3W7xJWVxuJhhlAlNxfWZfj6h19hMf18ppjgjR4XgB0ij2RrOch jcDO9JDXsMsxIkK8dsdrxr3JO+yAExYSVO9EIzmnD8YTQ9o7ObzRI1a0tgv3hhOy 3HT0JRFtm2tixEtMP292An4jpiz+2V6dH9aEkcig5SlJgudnuEo= =wJng -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/3e60deac-7cef-23fd-3b59-cd0467d5b79e%40qubes-os.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Openbsd as a netvm
On Thu, May 30, 2019 at 09:56:18AM +, ronpunz wrote: > I'm attempting setup a netvm using openbsd. > > I'm following Unman's guide > https://github.com/unman/notes/blob/master/openBSD_as_netvm but "fell at the > first hurdle" i.e. Line No1 states "Install OpenBSD as HVM Template". Does > this mean a standalone template? If so I've successfully completed this > stage, but, am unable to proceed to line No2 " Create netvm "openFW" using > OpenBSD as template" - as I understand it an appvm cannot be created from a > standalone template. That being the case, it looks like I need to create an > openbsd template - but how? I need either source code to build it or a > repository to download it? As far as I'm aware, neither exists? > > Any help would appreciated Those are notes, not really intended as a guide. What you need is: qvm-create --class TemplateVM openBSD --property virt_mode=HVM --property kernel='' -l purple qvm-create -t openBSD --property virt_mode=HVM --property kernel='' -l purple open -- 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/20190531005144.qeq3eldzwo7bn435%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Fedora 28 has reached EOL
Just one question: which Fedora version is dom0 based on? Is there some need for updates that I ignore? Bernhard -- 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/ba6a8f75-f0d4-b0c7-da3e-6404faa34774%40web.de. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Domain sys-net has failed to start: internal error: libxenlight to create a new domain 'sts-net'
rotellini9...@gmail.com wrote on 5/30/19 1:59 PM: I'm sorry for the stupid question but how can I go on qubes setting/devices tab.? Qubes menu (top left)/Sys-net/Sys-net:Qube Settings/Devices tab. Have you seen the Qubes documentation at https://www.qubes-os.org/doc/ ? It's pretty thorough, check out the PCI Devices doc for example. It describes in more detail how to go about attaching, etc. -- 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/0e054286-12be-3812-d825-c6bd4a11a373%40danwin1210.me. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Global Setting return error
scurge1tl wrote on 5/30/19 12:17 PM: 'awokd' via qubes-users: scurge1tl: The only thing I spotted to have issues, is the Global Settings button, which is not reacting. Check https://github.com/QubesOS/qubes-issues/issues/4988. Use "qubes-prefs" in a dom0 terminal as a workaround. Is there any guide of how to use the command? Most commands (including this one) in most distributions support appending "--help" or prepending "man" to get more information. -- 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/51c4cfcc-2075-33a6-af67-72103c976949%40danwin1210.me. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] dom0 kernel 4.19.43-1 update a fix for ATI Radeon cards, or the original?
drok...@gmail.com wrote on 5/29/19 3:09 PM: On Saturday morning, dom0 had a kernel update 4.19.43-1 which broke Qubes for people with older ATI Radeon cards. It was temporarily pulled. I see the same kernel is now back in the updates repository. Is this the same kernel which breaks ATI Radeon cards? Or is it a different kernel, that fixes the ATI Radeon breaking issue. I am afraid to install the update. If it is the same kernel (it is same number) it will break my Qubes install again. I am not looking forward to going thru all of that again. I checked on the open issues page, and didn't see any info on this update, one way or the other. If I missed it, I apologize. I'm fairly new to Qubes and still learning how support works. Are you sure it's not 4.19.46-3 (the fixed version)? -- 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/5eb538b9-3e49-3c3d-1f72-a3d0a7cb3214%40danwin1210.me. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-devel] Re: [qubes-users] Fedora 28 has reached EOL
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Thu, May 30, 2019 at 02:38:46PM -0400, Chris Laprise wrote: > > I'm getting strangeness from the fedora-30 release: > > 1. As soon as the template installed I started it and ran 'dnf update'. It > downloaded repo data then said 'nothing to do'. Less than 2 minutes later I > get a popup saying fedora-30 has updates available I run dnf update > again and there are 219 packages to update. This is dnf thinking metadata cache is up to date. dnf update --refresh should do the job. > 2. Trying to remove thunderbird, dnf wants to remove 67 packages incl. most > of qubes*, nftables, salt, tinyproxy. It would be good to be able to remove > thunderbird or other large apps without the OS crumbling to pieces. Try dnf --setopt=clean_requirements_on_remove=0 remove thunderbird clean_requirements_on_remove=True behaves like 'apt autoremove'. And qubes-vm-recommended depends on thunderbird-qubes, which depends on thunderbird. So when you remove thunderbird, qubes-vm-recommended needs to be removed too. - -- 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- iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAlzwJL0ACgkQ24/THMrX 1yyxjwf/V6DPJ7x7+e4IrO3vEeX+3iWHQLBg065Q1Z5lT/GU7Rw0Jsu0efP66VyA 71la73wl57cGkbbFT/zxvX7ivuyiIsFU2PvAsTbEBZ6GTUUzLZUU5MCdvmQ7ug1F C//vqz3Hwke+UaQ54D09Gx/ur67BEWve6aMQq9iwJMGgV9/jBtVRehQV1S/pGMLH AbNCwCeigTPdhK+i36gdHQByLPZ+9H4rpd0CdUzdaFiKY1d94SgLRPa2Roodpcc4 HstUhGtjKAyV4KVX7LSqbUwJLjGV1n6kLaWi81hHf7fWSSbyjLV0hTyBbOHj1S/s 19RAP3obd+q/blHeVilVBxWL5JJuWg== =m8oh -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/20190530184517.GK1793%40mail-itl. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Fedora 28 has reached EOL
I'm getting strangeness from the fedora-30 release: 1. As soon as the template installed I started it and ran 'dnf update'. It downloaded repo data then said 'nothing to do'. Less than 2 minutes later I get a popup saying fedora-30 has updates available I run dnf update again and there are 219 packages to update. 2. Trying to remove thunderbird, dnf wants to remove 67 packages incl. most of qubes*, nftables, salt, tinyproxy. It would be good to be able to remove thunderbird or other large apps without the OS crumbling to pieces. -- 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 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/0949b2a5-0555-6824-ad23-0f04aafead17%40posteo.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] R4 system requirements; AMD compatibility?
On Thursday, May 30, 2019 at 10:01:07 AM UTC-4, Claudia wrote: > 1) Should I update the BIOS before attempting to install Qubes? Is this > a generally recommended practice for Qubes, and if so, why isn't it > mentioned in the installation guide? I know you're asking Chris, so feel free to discount my comments here. :) My strategy before Qubes installation is: 1. Update the BIOS/UEFI PC firmware. Must be done on target workstation/server. 2. Update the SSD firmware. Can be done on a different workstation. 3. Reset the factory DEK on the SSD if it supports OPAL or OPALite. Can be done on a different workstation. 4. NEW: turn off hyperthreading in the BIOS/UEFI config. > I wonder how many people gave up on > a Qubes install without ever trying a firmware update. Should I keep the > firmware up to date thereafter? Firmware updates used to be rare, and it > was only recommended to install them if something was actually broken. I > guess now that the firmware is practically an OS in itself, we should be > updating it like one? I do, usually after some new Intel CPU vulnerability is published. :) > Luckily, Dell provides a way to update firmware from Linux, and a way to > do it with no OS at all. However, I imagine some (most) vendors require > Windows in order to install firmware updates. Just out of curiosity, how > do Linux users do firmware updates on machines without fwupd or a > self-updating firmware? I install a test Windows instance, download the firmware from the vendor and install it using the vendor tools. That's probably not the most secure method out there. > Also, what about microcode? Can microcode updates affect Qubes > compatibility? I know microcode is typically loaded by Linux each boot, > but if the system can't boot, I guess you have to install a permanent > update through the BIOS? One thing that enterprise-serving PC manufacturer *firmware* updates generally cover is the microcode updates. Dell, Lenovo, etc. generally update the firmware with the microcode. Sometimes the BIOS firmware might get the update first, sometimes Linux distros might. > 2) Do you think 4GB RAM will be enough to do the install? The system > requirements list 4GB as minimum, so I'm assuming it'll work. I'd rather > not buy the RAM until I know I'm keeping the machine, although I will if > I have to. But if I am going to need RAM for the install, I should order > it ahead of time. I semi-recently installed 4.0 (can't remember which ISO release) on a system w/ only 4GB of RAM and it installed fine. However, it freaked out trying to start up VMs, repeating and failing continuously. Part of the issue there, I think, is a defect that has already been fixed in testing (and recently pushed to current) where dom0 was reserved more RAM than necessary severing limiting RAM available to VMs. So for 4.0 I recommend at least 8GB and preferably 12GB. If you'll be running HVMs and/or Windows VMs that cannot participate in memory balancing like the PVH VMs can, 16GB minimum. 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 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/824c98c5-e15f-444c-a533-0a7af78d9f54%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Using sys-whonix with Windows AppVM
Hi Roger, > > Did anybody connect a Win AppVM to sys-whonix? Any additionnal steps that > have to be taken? Its difficult to tell what the problem is without system logs and/or error messages. You can take a look at the Whonix docs. (it is possible to do this). https://whonix.org/wiki/Other_Operating_Systems#Windows-Whonix-Workstation_.E2.84.A2 Regards 0brand -- GPG Public Key: 0x09B31BA99EC051FE Fingerprint: 4452 4D54 4EB2 53E8 1EE9 223A 09B3 1BA9 9EC0 51FE -- 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/59ae15bf-e5af-dc49-1820-92fb3248323d%40mailbox.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] R4 system requirements; AMD compatibility?
Chris Laprise: On 5/22/19 3:17 PM, Claudia wrote: Thanks for all the info! All good news except for the part about BIOS/UEFI feature support, which doesn't come as a surprise. I understand that, for maximum certainty, one should look at high-end, business-class, Linux-friendly product lines. However, this kind of defeats the whole point of looking for a laptop with a low-cost good-performance processor such as Ryzen. Those product lines are pricy to begin with (relative to specs), and they rarely ever go on sale. Also, it stands to reason that low-cost processors are usually found in low-cost machines. I found a couple of lists[1][2] of laptops with these processors. While there is a Thinkpad on the list, it looks to be mostly consumer-level laptops (although I'm not real familiar with computer makes and product lines so I could be wrong). To be honest, I was kind of looking this[3] Inspiron 5575 with 2500U available at Walmart for $350 (was down to $330 for a few days). After upgrading the RAM and perhaps adding an SSD, it still looks like a good deal for the money. Good enough to take a chance on, I think -- if it doesn't run Qubes, I'll just have to return it and look at some higher-end models. It sounds like you have an approach worked out. If the low cost model doesn't run Qubes, then consider: Now that AMD is being taken seriously for business laptops (where they used to be extremely rare), there should now be more choices that are lower cost _because_ they have an AMD processor. FWIW, firmware compatibility isn't good on consumer models regardless of the CPU vendor: Intel based consumer products suffer from it, too. (Sorry it took me this long to reply.) Indeed, that's what it sounded like to me from your initial reply. I was more worried about CPU vendor, mostly due to the way the system requirements page is worded, and lack of relevant search results for "Qubes on AMD." But as you pointed out, BIOS/UEFI support (and therefore, the specific computer/motherboard model) is a much more important consideration. So I'm glad I asked. Also, just out of curiosity, as far as consumer vs. business and firmware support: in your experience does firmware support also depend significantly on the vendor, and not just product class? e.g. perhaps vendor A's consumer-level products work even better than B's business-class. Do any particular vendors use generally "better" firmwares? (I know you mentioned Lenovo, Dell, and HP with regards to Linux support.) Or is firmware support about the same across vendors, within each product class? I did some quick searching, and Inspirons appear to have reasonably good Linux compatibility, at least for consumer-level laptops. Inspiron 5575 is even on the arch wiki[4] (which is definitely not conclusive, but a good sign nonetheless, no?) Dell is said to have a larger number of models that are _intentionally_ Linux compatible. Its worth checking their website to see if that model (or any adjacent to it) are labeled as Linux compatible. The Dell support page for Inspiron 5575 actually lists Ubuntu as a compatible OS... a good sign! Just to be clear, what relationship is there between Linux compatibility, and firmware support, if any? Are these the same thing? Roughly correlated? Or totally different? Good luck! And let us know how it goes and if you have any specific questions. I'll make sure to follow up. I'm waiting to order it until I know I'll have enough free time to play around with it, as I'll only have a limited time to decide if I'm keeping it or returning it. Hopefully within the next week or two. I thought of some more questions in the meantime. Hope you don't mind me picking your brain a little. 1) Should I update the BIOS before attempting to install Qubes? Is this a generally recommended practice for Qubes, and if so, why isn't it mentioned in the installation guide? I wonder how many people gave up on a Qubes install without ever trying a firmware update. Should I keep the firmware up to date thereafter? Firmware updates used to be rare, and it was only recommended to install them if something was actually broken. I guess now that the firmware is practically an OS in itself, we should be updating it like one? Luckily, Dell provides a way to update firmware from Linux, and a way to do it with no OS at all. However, I imagine some (most) vendors require Windows in order to install firmware updates. Just out of curiosity, how do Linux users do firmware updates on machines without fwupd or a self-updating firmware? Also, what about microcode? Can microcode updates affect Qubes compatibility? I know microcode is typically loaded by Linux each boot, but if the system can't boot, I guess you have to install a permanent update through the BIOS? These are just things I thought of and was curious about, but I guess I don't have to worry unless I actually hit a problem. 2) Do you
Re: [qubes-users] Domain sys-net has failed to start: internal error: libxenlight to create a new domain 'sts-net'
I'm sorry for the stupid question but how can I go on qubes setting/devices tab.? -- 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/b55a42d3-dc02-4630-ad2e-8cc1dadc63fe%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] No more updates for Fedora-29?
> The new Fedora 30 TemplateVM is currently in testing: > > https://github.com/QubesOS/qubes-issues/issues/4845 > > When it migrates to to stable, we will make an announcement, as usual. Actually, it is already in the stable repo: https://ftp.qubes-os.org/repo/yum/r4.0/templates-itl/rpm/ -- 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/df512507-a4e3-4d21-bee8-30ca149e1494%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Weird icon in Applications, behavior of the deleted VMs
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Yesterday I was experimenting with monero gui. I just unpacked the monero-gui-linux-x64-v0.14.0.0.tar.bz2 (the hash and PGP verifications were ok) in the AppVM named monero-on based on whonix-ws-14 and played with it for some time. Than I deleted the AppVM and shut down the laptop . Today, when I click on the Q icon Applications, I see a weird icon in the list between domain: and service: named "monero-on-vm", with a weird icon which looks like a box with trash or what. Options available are: monero-on: Chat support monero-on: Dolphin None is working when clicked. I thought the Q button Applications is under control of dom0 and there is no way how the monero-gui-linux-x64-v0.14.0.0.tar.bz2 would influence dom0 this way. I don't know if it is related, but when booting to Qubes, and watching the boot process, I can still see Qubes is trying to boot AppVMs which are for months deleted, with "Failed to start" the VM. How do I delete it permanently? Can you advice me how to work it out, and put a bit light into the matte r? Thank you! -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEExlmPb5HoPUTt+CQT44JZDAWK6UwFAlzv0AFfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEM2 NTk4RjZGOTFFODNENDRFREY4MjQxM0UzODI1OTBDMDU4QUU5NEMACgkQ44JZDAWK 6Uz6nQ//T7N8S/u+mCX6hCwCI+e6GSW7WdOiFygmWV6IoPA+UnX5K3ypracVyiQM DidkaqLYP4Nr5sH3h4WvYcD1Gpr4lv5PCIB5Gc/3g2pe0N+iv6FAfFDz/0T4shGM xhbjux9mQPXFTcvRNSiyDsUYIl7QNf+iMXnDMwdsCCBLkm7tblxRxmSWy+/mkKML ceTm7Wt/6TsOk/oMvMWtDIf1V7ud9GeGUyNmrZUuh+nBsHxvCndOdmWYkswuvSir oGkBAgyg3iAYfBLSMeBPAzMyYnGoSqx1OP3qxozKNyGh9cIZuBvQfDMTyJQjK2f1 vaOTCh9Ia2IRK9nrynG5QnI+iWXKZnZAlWTFrZ6Rr5Ghg5SQgyGhr55ERb5e+QiE HveE6jvAwoF2qmYk+YeeWjzc3Fe1doeNEmTyNGO103td5uxiuZ96c3kOfW6q0uCc sRHpBgM4/gToeDEB93c1TVUU4h+b847yROBC0kfz7k2WyYqSnIyHO9NODrpDGY3P On56xqYA6pwzuLLsDToSz001bNMfMKtTtMuL1jkhsGXpxj77P7pBUhK6zLSnZxys BA5w7HFQEmICH/+A4QLsRYvra4CFeVXv392MXOdlXa3y8V+zQTaAzaYiAC1NqV99 rYE4QNh4X8GbAsY/IcqZYoJvVvgNVAWijRSYhxXL12YUA0Eeczs= =GZCa -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/0acf14dd-f40d-06d7-1381-dfde3447da78%40cock.li. For more options, visit https://groups.google.com/d/optout. 0xC1F4E83AF470A4ED.asc Description: application/pgp-keys
Re: [qubes-users] Global Setting return error
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 'awokd' via qubes-users: > scurge1tl: >> The only thing I spotted to have issues, is the Global Settings >> button, which is not reacting. > > Check https://github.com/QubesOS/qubes-issues/issues/4988. Use > "qubes-prefs" in a dom0 terminal as a workaround. > Is there any guide of how to use the command? -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEExlmPb5HoPUTt+CQT44JZDAWK6UwFAlzvyelfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEM2 NTk4RjZGOTFFODNENDRFREY4MjQxM0UzODI1OTBDMDU4QUU5NEMACgkQ44JZDAWK 6UwYmRAAni+FSOEFrK36yX4MzPkk5fFBCWD2rYTYpuKmPHDakf4hjcSIDPvFTYHQ kl5rCXopsbVF+aApjvnzdRwvPdX0oLzp57PQ983tFPS+HRjjd/HFnGiNioStF9F4 L75xReFyeMVHG6M5t7xWh+t4j1Q6v8o+H+T3JVeOHSI5n1KvDgq0u1EggSrrqsW4 1ADcJWBlC4ynrAIf+fjyUUcOFh8f4CvR9/iSZq0zVM8v527szPsuQjhXdYzbHz78 rfZWme1E1gBn2ZitOKpQql9qaEqQLn3eCFjRil8oM935LkOANUprCyGRC4zjC3tv etuBIYRB278BYwj6TPd/jXmFYjDrsHLecJGFBlEXXDT8FtqCCbllhApz9OcdTFLp SVsUoHOUpHaS+sMYPvinZ3uzIbVZSmBJy0/SgJEnG8AispyrXkKNNHYnJ9EXE8LW x9ef5pfP6n0gzAx5SKw85NaiHaLOSsarFaw+rkEAJZD4kPS1vGKjQYeL589SvZ+V e6V+mD+2gMcF2iNVtYGXV+zoBnPVU7I4z4CG9bJVCMVYycbt9/zHm4fFAuZyS9Ys 64eKKySIfuWQFKBkvUGMYDGegPICJtoSEFvkf4rJibvP9l7at1Gj6wispbWN001B +nDaq8azUACjv1YNfV1N3AeF7oWzJADcvotyYtpv/+cfS7DBqjA= =gVM1 -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/13fe4684-2b46-3396-076e-219089f51069%40cock.li. For more options, visit https://groups.google.com/d/optout. 0xC1F4E83AF470A4ED.asc Description: application/pgp-keys
Re: [qubes-users] Re: real and virtual storage usage by qubes
On Tuesday, May 28, 2019 at 7:25:46 PM UTC-4, Chris Laprise wrote: > > If you run fstrim -av inside the qube, it's supposed to release unused > > space back to the thin filesystem. > > Keep in mind this will probably cause the volume to consume more LVM > metadata or 'tmeta'. The filesystem probably avoids sending trim/discard > for smaller chunks to avoid filling up the tmeta area (at which point > the storage pool becomes unusable). > > Thread > https://groups.google.com/d/msgid/qubes-users/44f1ae64-2da1-480f-aa30-98c5f22653ba%40googlegroups.com Which reminds me, Chris, since you asked over on that thread: The sudo lvs output on my primary qubes install shows 29.79 under the Meta% column for the pool...and I'm possibly the most frequent invoker of fstrim in the Qubes userbase. Granted, the Data% is at 25.85, which is smaller than the Meta%, so that probably says something not so great about data loss risk as the pool fills up... 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 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/2eb64024-4893-4402-a064-3f5563a9f246%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Openbsd as a netvm
I'm attempting setup a netvm using openbsd. I'm following Unman's guide https://github.com/unman/notes/blob/master/openBSD_as_netvm but "fell at the first hurdle" i.e. Line No1 states "Install OpenBSD as HVM Template". Does this mean a standalone template? If so I've successfully completed this stage, but, am unable to proceed to line No2 " Create netvm "openFW" using OpenBSD as template" - as I understand it an appvm cannot be created from a standalone template. That being the case, it looks like I need to create an openbsd template - but how? I need either source code to build it or a repository to download it? As far as I'm aware, neither exists? Any help would appreciated -- 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/c5d653e9-6e2d-33ad-8140-4b7cf49aa8cd%40riseup.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Openbsd HVM - Network Issues
On 5/29/19 11:36 PM, 'awokd' via qubes-users wrote: ronpunz: SOLVED I had mirage-firewall set as the default netvm. I changed the openbsdVM firewall to sys-firewall and the network now works fine. Noticed Mirage firewall 0.6 had a couple bugfixes for HVM support. Since you upgraded, maybe it would be OK to switch back now. Yes, you're right. Switching to mirage-firewall now works. You need to be aware though that a revised gateway will be issued - which needs entering into openbsd's /etc/mygate. 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 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/6f911365-ca57-dcc4-34ec-8e29a56d83ba%40riseup.net. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Using sys-whonix with Windows AppVM
Hi When I attach the Personal AppVM to sys-whonix, I am connected to Tor (check.torproject.org). However, when I connect sys-whonix to a Win10 AppVm, Windows tells me that it has no internet. Something with the gateway, I think? Did anybody connect a Win AppVM to sys-whonix? Any additionnal steps that have to be taken? Thank you for your help Roger -- 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/a2756d79-2269-4b67-a771-7cfb2eb79981%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
