[qubes-users] Whonix 15 has reached EOL

2021-11-14 Thread Andrew David Wong

Dear Qubes Community,

Whonix 15 has reached EOL (end-of-life). If you have not already done
so, we strongly recommend upgrading your Whonix 15 templates and
standalones to Whonix 16 [1] immediately. The Whonix Project provides
fresh Whonix 16 template packages through the Qubes community template
repositories, which you can install in dom0 by following the standard
installation instructions [2]. Alternatively, the Whonix Project also
provides step-by-step instructions for performing an in-place upgrade
[3] of an existing Whonix 15 template. After upgrading your templates,
please remember to switch all qubes that were using the old template
to use the new one [4].

For a complete list of template releases supported for your specific
Qubes release, please see our supported template releases [5].


[1] https://www.qubes-os.org/news/2021/09/30/whonix-16-template-available/
[2] https://www.whonix.org/wiki/Qubes/Install
[3] https://www.whonix.org/wiki/Release_Upgrade_Whonix_15_to_Whonix_16
[4] https://www.qubes-os.org/doc/templates/#switching
[5] https://www.qubes-os.org//doc/supported-releases/#templates

This announcement is also available on the Qubes website:
https://www.qubes-os.org/news/2021/11/14/whonix-15-eol/

--
Andrew David Wong
Community Manager
The Qubes OS Project
https://www.qubes-os.org

--
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/d7baaf3f-bb3f-64fd-a68f-e13b93f207fb%40qubes-os.org.


Re: [qubes-users] [HCL] ASRock B550 Phantom Gaming 4/ac

2021-11-14 Thread 'awokd' via qubes-users

awokd:

Vít Šesták:

Hello,
I'm posting HCL report for my computer with this ASRock B550 Phantom 
Gaming

4/ac and Ryzen 7 5800X. I've few comments:


Short reasoning why I decided for this MoBo: ECC support for a good 
price.


Interesting.

Were you able to verify ECC function under Qubes? If so, how? 
Documentation I'm finding indicates there is no Xen level support for 
ECC, so it would be up to the BIOS to log any memory bit errors.


--
- don't top post
Mailing list etiquette:
- trim quoted reply to only relevant portions
- when possible, copy and paste text instead of screenshots

--
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/e5de0e07-4434-c8d3-a9cf-fa634af879c3%40danwin1210.me.


Re: [qubes-users] Tor bridge/entry node/relay question

2021-11-14 Thread 'awokd' via qubes-users

'gray' via qubes-users:

 I also tried 
[this](https://github.com/Osndok/qvm-expose-port/blob/master/qvm-expose-port), 
which I think is equivalent to the third section of the Qubes Firewall 
page. I tried `qubes-expose-port` both from the guest and from dom0. 
When run in dom0, it tells me I need to expose the physical networking 
device, as well, which I didn't know how to do (so perhaps it would work 
when run properly from dom0).


The above should work if you are exposing ports on the standalone qube. 
Is it directly attached to sys-firewall? If not, it should be. Dom0 is 
not the right place; as you noted, it intentionally has no networking.


--
- don't top post
Mailing list etiquette:
- trim quoted reply to only relevant portions
- when possible, copy and paste text instead of screenshots

--
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/adf399f9-ab85-f2ef-7bed-6965e6de852d%40danwin1210.me.