[qubes-users] HCL : NitroPC 2 - MSI Z790-P Intel i9 14900K
HCL report NitroPC 2 - MSI Z790-P Intel i9 14900K This is Qubes certified, of course, but here's an HCL report anyway. --- layout: 'hcl' type: 'Desktop' hvm: 'yes' iommu: 'yes' slat: 'yes' tpm: 'unknown' remap: 'yes' brand: | Micro-Star International Co., Ltd. model: | MS-7E06 bios: | Dasharo (coreboot+UEFI) v0.9.1 cpu: | Intel(R) Core(TM) i9-14900K cpu-short: | FIXME chipset: | Intel Corporation Device [8086:a700] (rev 01) chipset-short: | FIXME gpu: | Intel Corporation Raptor Lake-S GT1 [UHD Graphics 770] [8086:a780] (rev 04) (prog-if 00 [VGA controller]) gpu-short: | FIXME network: | Intel Corporation Ethernet Controller I225-V [8086:15f3] (rev 03) memory: | 65376 scsi: | usb: | 1 certified: 'no' versions: - works: 'yes' qubes: | R4.2.1 xen: | 4.17.3 kernel: | 6.6.21-1 remark: | No problems noticed. Qubes certified. Very Fast. credit: | code9n link: | FIXLINK -- 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/54d6b847-4390-45c1-ac7a-b35347d76713n%40googlegroups.com.
[qubes-users] HCL Purism Librem mini V2 with Qubes 4.2
Hi, HCL: --- layout: 'hcl' type: 'Desktop' hvm: 'yes' iommu: 'yes' slat: 'yes' tpm: 'no' remap: 'yes' brand: | Purism model: | librem_mini_v2 bios: | PureBoot-Release-20 cpu: | Intel(R) Core(TM) i7-10510U CPU @ 1.80GHz cpu-short: | FIXME chipset: | Intel Corporation Comet Lake-U v1 4c Host Bridge/DRAM Controller [8086:9b61] (rev 0c) chipset-short: | FIXME gpu: | Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) gpu-short: | FIXME network: | Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 07) memory: | 65410 scsi: | Samsung SSD 870 Rev: 1B6Q usb: | 1 certified: 'no' versions: - works: 'yes' qubes: | R4.2.0 xen: | 4.17.2 kernel: | 6.1.62-1 remark: | Everything seems fine credit: | code9n link: | FIXLINK .cpio attached. Thanks for 4.2 On Sunday, January 21st, 2024 at 09:45, qubes-users@googlegroups.com wrote: > [qubes-users@googlegroups.com](https://groups.google.com/forum/#!forum/qubes-users/topics) > [Google Groups](https://groups.google.com/forum/#!overview) > https://groups.google.com/forum/#!overview > [Today's topic summary] > [View all topics](https://groups.google.com/forum/#!forum/qubes-users/topics) > > - [problem with 4.2 rc5 installation source](#group_thread_0) - 1 Update > [] > [problem with 4.2 rc5 installation > source](http://groups.google.com/group/qubes-users/t/2d918d15d2aebc4e) > Kai : Jan 20 02:26PM -0800 > > Thank you to everyone who has helped me in the last mails. > > I have finally decided to buy a NovaCustomes Laptop that is Qubes certified > and as expected, that works very well with Qubes 4.2. > [...more](http://groups.google.com/group/qubes-users/msg/1949463a81fdf) > > [Back to top](#digest_top) > > You received this digest because you're subscribed to updates for this group. > You can change your settings on the [group membership > page](https://groups.google.com/forum/#!forum/qubes-users/join). > To unsubscribe from this group and stop receiving emails from it send an > email to qubes-users+unsubscr...@googlegroups.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/fD3uWIfDS2n70LKl7Fs9ECBCdjM1bf2gFtuqgn6TjFXN9jCajii2IL0iL4Qiw0qU9DYlHJoxp1j1wG2REIGn4PCumbrxgDriDBnjm8vHJHQ%3D%40protonmail.com. Qubes-HCL-Purism-librem_mini_v2-20240121-180500.cpio.gz Description: application/gzip
[qubes-users] Re: Qubes 4.2: qubes-tunnel not working after upgrade (cannot resolve hostname)
Hi, This is on the Forum: https://forum.qubes-os.org/t/wireguard-vpn-setup/19141 cheers, On Saturday 6 January 2024 at 00:16:40 UTC r.wie...@web.de wrote: > Hi there, > > vpnVM and netVM both in-place upgrades from Q4.1 (and worked fine > there). Template is fedora 38. > NetVM is online, ping of vpn server hostname is fine within netVM. > Ping and dig do not work within vpnVM, but afair that is intended (leak > prevention of qubes-tunnel) > > I tried to restart qubes-tunnel servcie, tried to restart vpnVM. tried > to disconnect and reconnect. I tried to reboot QubesOS. > > Did something change between 4.1 and 4.2 regarding DNS handling? Do I > need to configure a policy file or something? > > 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/d4f11ed1-dcfe-45ef-b318-49b7416a6801n%40googlegroups.com.
Re: [qubes-users] 4.1 rc1 'start automatically on boot' saving abnormality
Hi, Qubes manager version: qubes-manager-4.1.19-1.fc32.noarch . Start qube automatically on boot: On a normal default app qube based on a template, either fedora or debian, either running or not running. Steps: 1) Highlight the qube I want to get to open automatically on boot in the Qubes manager. 2) Click on the 'Qube Settings' cog button and the manager opens to the 'Basic' page. 3) Click to check the 'start qube automatically on boot' box, the check mark appears. 4) Click on 'Apply'. The system working icon appears, the change looks to be working but then the check mark disappears. 5) Click on 'OK' and the manager window closes, the desired change has not happened. However if I click on just the 'OK' button the change is saved correctly. Or, if I don't give up so easily and try checking the 'start qube automatically on boot' again, then clicking 'Apply' again, then 'OK', the change is saved. I have done this many times in writing this and the behaviour seems to continue with the 'start qube automatically on boot', action. However the same thing was happening with saving a networking selection but that has mostly corrected itself: Networking: The networking selection - as above but changing a qube's networking choice, from, eg. 'sys-vpn' to 'firewall' - was doing the same behaviour as above. But now it looks like the action will not be saved - I make a selection, the 'networking' menu shows the 'sys-vpn (current)', option. I choose 'firewall', and click 'Apply'. The 'system-working' icon appears. The 'system-working' icon disappears and the selection I made - 'firewall', reverts to 'sys-vpn'. So it appears my action failed. But when I click, 'OK', the change has successfully happened. Thank you, and I'm loving 4.1. On Friday, 5 November 2021 at 00:46:42 UTC marm...@invisiblethingslab.com wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On Thu, Nov 04, 2021 at 03:16:22PM -0700, code9n wrote: > > Note: Made a Tasket Qubes vpn support networking qube on Qubes 4.1 rc1 > > which works efficiently as always but when I check the 'start qube > > automatically on boot' box in Qube Settings / manager gui it won't save > if > > I click on 'apply' first. > > But it will save if I just check the box then click directly on 'OK'. > > Can you provide exact steps you've done? Which buttons and in which > order you clicked? I just tried and clicking 'apply' just after > selecting 'start qube automatically on boot' does save the setting for > me. > > What qubes-manager package version you have, you can check it with > `rpm -q qubes-manager` command. > > - -- > Best Regards, > Marek Marczykowski-Górecki > Invisible Things Lab > -BEGIN PGP SIGNATURE- > > iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAmGEfuoACgkQ24/THMrX > 1yxljQf9EVaX9aJGRaY7KPp8Zl+d4V01MSdoKLM0BsG0I1jiY++yLdBn+SlGCI6p > OjklXd0RmhRfTF+wQ/PZ0UTF3UkccClgd8DQ4pIncQYQIfH190ZhRbsp2Fl5qGnZ > O7NUZXJk/iH6/MZYu+rV9ydtaQd1yhhDgCI78p5HdrQkAjoOPy0xemEoQks1jHTY > 3+UrKuC3qdWiNBNmfxNd88wvppbki9uDW8HRnCHcgYFdaYhYmHhnVpzY5IMTjVqs > p+k+uiBnJ22KG2PqI7hgYJQdEThyLJdX3iNJbwscRGFNoxPlIY8qQSOCrnC1GARB > M7535Ox00MkLtbTMjuncw9H76hSD8w== > =YTsL > -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/93ac8e99-6591-4682-a4aa-651d2cabdb53n%40googlegroups.com.
Re: [qubes-users] 4.1 rc1 UK keyboard reverted to US layout
Thanks, For what it's worth this can be solved by going into the System tools - Settings manager - Keyboard - Layout where it is set to 'English UK' already. Click on edit, the existing 'English UK' option comes up on the pop up menu, then just leave it on that and click on 'OK'. Now it actually does use the English UK layout. Apologies if I should have answered this in a different place. On Friday, 5 November 2021 at 00:42:54 UTC marm...@invisiblethingslab.com wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On Thu, Nov 04, 2021 at 03:10:20PM -0700, code9n wrote: > > > > Note: I carefully made sure the GB / UK keyboard option was selected > > during install but have the US set up on my UK keyboard Lenovo T430. > > Looks like this issue: https://github.com/QubesOS/qubes-issues/issues/6814 > > - -- > Best Regards, > Marek Marczykowski-Górecki > Invisible Things Lab > -BEGIN PGP SIGNATURE- > > iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAmGEfgYACgkQ24/THMrX > 1yxdAgf+LBOJK4Sp2hv5FS2zz/8XRN+QktbnvXh4MeOrJ7iGEAC+5i6+wvEjEUN7 > IFk+KNtCoknHwwtQXd/9PZwdcx3kO9KfS0BrQ8HNjSK/sh/rM+qC5vRRdU6UyxFK > goK7r0W7R9lWJwdxfQ0gzZZa3UlidwVTuG2s9hecpsh7Fdxd1OKx2DzVZU3jPacN > S6ea+t5I8MaLnOA6X0OaQBXMLRJNOId9glzAOrKtfsL7nQ8IZ5kzZV2ClJvbMe91 > fEaaVVnSwssrYDt95k1/Xb/flclFydRwkZuLMUd90COOAEENxt12qGNVWin9sk3Z > RwOAc9zf0P1nGq0tN/qfkOfZZUfpew== > =D5Xk > -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/84b95e77-0c35-49da-a9cc-aa4a88dcdb95n%40googlegroups.com.
[qubes-users] 4.1 rc1 'start automatically on boot' saving abnormality
Note: Made a Tasket Qubes vpn support networking qube on Qubes 4.1 rc1 which works efficiently as always but when I check the 'start qube automatically on boot' box in Qube Settings / manager gui it won't save if I click on 'apply' first. But it will save if I just check the box then click directly on 'OK'. -- 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/0dd4fe08-91c6-4242-b5b9-e541357c6bd5n%40googlegroups.com.
[qubes-users] 4.1 rc1 UK keyboard reverted to US layout
Note: I carefully made sure the GB / UK keyboard option was selected during install but have the US set up on my UK keyboard Lenovo T430. -- 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/18ea5ac6-047a-46cd-94d4-2ff8e29a6188n%40googlegroups.com.
Re: [qubes-users] HCL Intel core i7-6700K in desktop machine (not laptop)
Amendment: I forgot, there was one installation problem - I couldn't get sys-USB to work, had to do it after install. Sorry about that. On Sunday, 8 August 2021 at 02:21:23 UTC+1 sv...@svensemmler.org wrote: > Thank you code9n for your HCL report, which is now part of [this pull > request](https://github.com/QubesOS/qubes-hcl/pull/87) and will be > visible on the website soon! > > As soon as there is a second report for this machine we can add it to > the "just works" list. Your having explicitly mentioned that your > machine fulfills the requirements makes this very easy. Thank you again! > > -- 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/ab3cd061-f15e-467e-9deb-d4477719b44cn%40googlegroups.com.
[qubes-users] HCL Intel core i7-6700K in desktop machine (not laptop)
Machine made with Qubes 4.0 in mind by Think Penguin - around a year before Qubes 3.2 reached EOL. Hope this is helpful. Thanks to all involved in Qubes OS. If your machine fulfills these criteria: * Qubes OS R4.0.4 installs without any workarounds - YES * Graphics, networking & audio work without troubleshooting - YES * Recommended 16 GB RAM are possible - 32 GB RAM --- layout: 'hcl' type: 'desktop' hvm: 'yes' iommu: 'yes' slat: 'yes' tpm: 'unknown' remap: 'yes' brand: | MSI model: | MS-7994 bios: | 5.80 cpu: | Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz cpu-short: | FIXME chipset: | Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers [8086:191f] (rev 07) chipset-short: | FIXME gpu: | Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA controller]) gpu-short: | FIXME network: | Intel Corporation Ethernet Connection (2) I219-V (rev 31) Qualcomm Atheros AR928X Wireless Network Adapter (PCI-Express) (rev 01) memory: | 32654 scsi: | WDC WDS500G1B0A- Rev: 10WD ST2000LM015-2E81 Rev: SDM1 iHAS124 F Rev: CL9M usb: | 3 versions: - works: 'FIXME:yes|no|partial' qubes: | R4.0 xen: | 4.8.5-34.fc25 kernel: | 5.4.129-1 remark: | FIXME credit: | FIXAUTHOR link: | FIXLINK -- 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/17ff41df-9bf5-4037-8d67-06a474a3e562n%40googlegroups.com.
Re: [qubes-users] Re: my dom0 is not updating since before 4.01
Having this same (old now) problem. Tried adding --releasever=4.0 to sudo qubes-dom0-update and I get most of the update to download but not all of it. Unman suggested : "you could manually download it, copy it to dom0, check signature in dom0 with rpm -K, and then install." Which apparently worked but how do I go about that? What package am I looking for and where do I look for it? If you could suggest commands to be used that'd be great? 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/4ac70d5b-c29d-457f-bffe-2e3553ea0c95%40googlegroups.com.
Re: [qubes-users] Fedora 28 has no audio on Qubes!
The pulseaudio issue was fixed in August? I've been waiting for that since the upgrade to fedora 27. Looked out for it in every fedora update and never saw it. (Now using fedora 28 - still no sound) - All updates completed that I know of. Do you need to have the Qubes 4 developers repository enabled? Or is there some way to install the fix another way? Complete re-install of the fedora 28 template? 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 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/7a51e91a-730f-47f5-9431-35446b564df6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] setting up vpn issue
Hi Nick, In case it's any use to you; I had a couple of vpns working on Q3.2 until about a week ago (moved to 4.0) and one of them was Expressvpn. What I did to set it up: Make a clone of my up to date fedora template ( or use Debian or whatever you like). Allow network access in that template. Then put firefox in the template's applications (and set up it's privacy to your liking) - you need only go to the Expressvpn's https site - and you're going to trust them anyway. (Plus it's a clone template.) Install Expressvpn following their instructions for the linux (appropriate Fedora package) into that template from their website. Then follow the easy instructions (Expressvpn site) and activate on the template. If you want to you can now connect to the vpn - expressvpn connect - in the command line of the template and go to (for example), https://www.dnsleaktest.com/ in your firefox to test it's working ok. . Close network access again on the template. Then make a proxy vm based on that new clone template as described in the qubes documentation: https://www.qubes-os.org/doc/vpn/ Set it with sys-firewall as it's netvm. Then connect to Expressvpn in your new proxy (I called mine sys-vpn-exp) - to get a list of commands - expressvpn help - in the command line. Set any appvms you want to go through that new proxy vpn (sys-vpn-exp) to have it as their netvm. Then open firefox in one of the appvms that go through your new sys-vpn-exp proxy and to test it - personally I mostly use: https://www.dnsleaktest.com/ or Expressvpn have their own dns leak test facility. Where ever. . The Expressvpn site has instructions for qubes but they want you to set up in the sys-net vm which means everything goes through them. I do it the above way because it's easy and you can use other vpn providers as well for some of your other appvms if you want to. It works fine. Or you could use: https://github.com/tasket/Qubes-vpn-support as suggested above - I use that for one of my vpns in Qubes 4 and it's excellent but it's more involved. Also harder to change which server / country you want to come out of. cheers, -- 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/fbc47b88-00dd-4a74-8feb-6e6a41b07f9c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Whonix 14 - Updated, just lost Tor Browser for Whonix-dvm??
I gave up on trying to back date whonix - there's so much about it on Whonix / Whonix-Qubes website and warnings about messing with the clock in Whonix ws konsole I didn't want to mess about. Tried (in Whonix ws) update-torbrowser chosing 7.5.6 but got the signature expired message so in the end I just went with 8.a10 which propagated fine into the whonix dvms. (There was a message somewhere on torproject.org website saying that 7.5.6 signature was about to run out so maybe it's just over due). TTB 8 is still in alpha theoretically but has worked fine for me and is apparently scheduled for release next month anyway. Just as a side note 'cos it seems relevant; When I updated Whonix to 14 a few days ago I kept the anon-whonix app vm with the 7.5.6 browser in it and although that is now based on Whonix 14 it kept ttb 7.5.6 which also runs fine. so it's not taking it's version of ttb from the Whonix 14 template but keeping the version of it's own. cheers, -- 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/d002af71-0258-4f20-86a6-24327224ae82%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Whonix 14 - Updated, just lost Tor Browser for Whonix-dvm??
Same issue but when I try to update-torbrowser (or via Tor Browser Downloader) the install fails because ttb's signature has expired. I have to wait for the tor project to resign ttb (7.5.6), right? If I tried to get the key that comes with it from torproject.org and import it into Whonix it'd still be the same, expired, key anyway? 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 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/b0f397f1-4401-47c1-a0aa-163b85593b0f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Fresh r4 install qrexec daemon fails to start. Any suggestion?
Thanks, you're right. I remembered I had the same problem when I installed 3.2. Disabled wifi adapter in sys-net and it worked. Same this time. Probably because I haven't got a wifi card - it's a desktop and I only use an ethernet cable. -- 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/e36a506a-8506-4596-ab49-128ba3111339%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Fresh r4 install qrexec daemon fails to start. Any suggestion?
Hi, I made r4 installation USBs many times to install r4 over the last couple of days - first fedora media writer in Q3.2, then from Windows with rufus with several different USB sticks and several different downloads. The downloads always completed properly, like wise writing onto the USBs. But every time I install r4 all goes well until after the reboot part of the install when the 'Qubes Install' window comes up. After this runs ok for a while, dealing with fedora 26, debian 9 and whonix templates - it gets as far as (something like) 'setting up network' when I get an error box with, [/usr/bin/qvm-start', 'sys-firewall'] failed: stdout:"" stderr: "Cannot connect to qrexec agent for 60 seconds, see /varlog/xen/console/guest-sys-net.log for details Then when I move on and Qubes opens the qrexec daemon won't run when called. eg. Following installation guide, when I get to: sudo qubes-dom0-update It tries to open sys-firewall and I get pretty much the same error message: ERROR: Cannot connect to qrexec agent for 60 seconds, see /var/log/xen/console/guest-sys-net.log for details (Waiting 60 seconds does nothing more.) Has anyone dealt with this or have any suggestions? 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 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/bf3fdbc8-0335-47e7-b688-9dc7af1f0405%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Qubes canary over due...
...but only by a day (see Qubes canary #14 - https://github.com/QubesOS/qubes-secpack/blob/master/canaries/canary-014-2017.txt) -- 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/0e3fcb65-8058-4d5f-96d0-b852ddff5f40%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Anon-whonix browser fails to connect to tor in Qubes 3.2, any ideas?
Solved. Not sure if it was relevant but since the most recent Whonix updates this has gone back to normal. Thanks to all. -- 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/9dd5a721-bb5d-4e88-9b66-c4b567c9621b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Anon-whonix browser fails to connect to tor in Qubes 3.2, any ideas?
Yeh, the anon-whonix app vm is routed through sys-whonix properly. I haven't changed that from default. I do route most non-whonix app vms through a vpn in a proxy vm but that all works as it should. Both systems have worked independently and as expected for months. Checking today some IP address checks in the anon-whonix app vm do come out in places other than Germany but they're not my vpn's servers, or my ISP's. It's like tor is mostly working but not fully. I'll leave this help request here and see if there are any more suggestions but if I have to I'll try deleting the var/lib/tor file contents - the tor data file mentioned above - and if it doesn't work try re-installing all the whonix stuff. 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 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/5a5d2c4f-a3db-4579-8ed0-74e573c8e574%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Anon-whonix browser fails to connect to tor in Qubes 3.2, any ideas?
Running the WhonixCheck from the default anon-whonix app vm in the Qubes manager list; the fail warning basically says: SocksPort test [fails]. ... (curl exit code: [7] - [failed to connect to host]) The browser - anon-whonix app vm (default)/Tor browser - opens like normal to the Whonix page but checking the 'check IP' link from there won't connect and if I search for https://check.torproject.org the top result says I'm not using tor. I can't connect to .onion sites but surface browsing's fine. Checking the IP address keeps coming back to the same one in Germany even if I reload / change Identity / reboot. (I'm not in Germany). It persists over cold re-boots. I've tried making a new anon-whonix app vm with the same results. Everything has been fine since install - maybe 6 months ago. All updates are up to date including the recent tor browser update to 7.5 (64 bit). yzxd on the sub reddit (Thanks, yzxd) had a similar problem on non-Qubes Whonix and solved it by "going into the Gateway VM, stopping Tor, opening the folder named "Tor Data" and deleting all the files inside, and finally restarting Tor". But I see from issue #1137 the Qubes team deliberately made that persistent: https://github.com/Whonix/qubes-whonix/commit/a9f24f5d0b700a0cd710e52eb170875d635c22a9 so I'm wary to mess with that. Would that be likely to work in this instance? Or Does anyone have any ideas for a fix or would just re-installing the entire Whonix system following: https://www.qubes-os.org/doc/whonix/install/ be better...? 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 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/6978414b-9934-40e3-96c9-403488a2e332%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
