Re: [qubes-users] Re: HCL - Hewlett Packard HP Pavillion Notebook

[Raja Saham]

Thank you for your information.
Okay, I will let the HCL maintainer determine.

Thanks and Best Regards,


On Mon, Nov 23, 2020 at 2:37 PM Andrew David Wong  wrote:

> On 11/23/20 2:55 AM, Raja Saham wrote:
> > May I know the procedure to add this report into hardware compatibility
> > list ?
>
> Thank you for your report!
>
> Our HCL maintainer periodically collects all reports sent to this
> mailing list and submits them in a pull request to:
>
> https://github.com/QubesOS/qubes-hcl/tree/master
>
> However, if you prefer, you can simply submit a PR there yourself.
>
>  > And whether it is qualified for the list ?
>
> That'll be up to our HCL maintainer to determine, but usually reports
> are accepted without any problems.
>
> >
> > On Monday, November 23, 2020 at 5:44:13 PM UTC+7 Raja Saham wrote:
> >
> >> Dear Qubes Users,
> >>
> >> I have tried Qubes on my System.
> >> Attached is the report for Hardware Compatibility List.
> >>
> >> Regards,
> >> Qubes Users
> >>
> >
>
> --
> Andrew David Wong (Axon)
> Community Manager, Qubes OS
> 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/CA%2BXFw%3DX6qrfLKKSbHpDUz0zL-1XfKCqZfwMqOhSbi_1HB6M0dg%40mail.gmail.com.

Re: [qubes-users] Xfburn not seeing usb

[Shawn Creighton]

I installed gnome-disk-utility and it sees the usb so I was able to format 
it, but when I try to flash it the .iso I downloaded is grayed out. Any way 
to make that accessible?

I don't have a sys-usb, just sys-net and sys-firewall. I tried running sudo 
qubesctl state.sls qvm.sys-usb but it didn't work, output says something 
like:

the following requisites were not found: 
require:
sls: qvm.sys-net



On Tuesday, November 24, 2020 at 3:43:12 PM UTC-6 stevenlc...@gmail.com 
wrote:

> You may need to run the software in the VM which contains the physical 
> hardware (e.g. the USB controller}. Passing a memory device generally works 
> but when you need special access to the physical hardware such as burning a 
> DVD then this pass-through method may not work correctly. 
>
> If your USB controller is in sys-usb then running Xfburn or Brasero there 
> is the best option. If not, and you have several USB controllers, you might 
> want to investigate creating a sys-usb for that purpose. Otherwise then you 
> may need to decide if you want to install a DvD burning package directly in 
> dom0, which generally should be avoided if possible. 
>
> Steve
>
>
> On Tue, Nov 24, 2020 at 2:26 PM Shawn Creighton  wrote:
>
>> Trying to create a bootable usb, installed Xfburn and connected the usb 
>> to the AppVM but when I open Xfburn as root it doesn't see the usb and says:
>>
>> "no burners currently available, possibly the discs are in use and cannot 
>> get accessed"
>>
>> Also tried installing Brasero which won't burn to usb 
>>
>> -- 
>> 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...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/qubes-users/9d137cef-525f-48bf-bd49-85c17ad02b9an%40googlegroups.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/6d9744ce-9319-4a59-90fa-a0a576cd3974n%40googlegroups.com.

Re: [qubes-users] Xfburn not seeing usb

[Steve Coleman]

You may need to run the software in the VM which contains the physical
hardware (e.g. the USB controller}. Passing a memory device generally works
but when you need special access to the physical hardware such as burning a
DVD then this pass-through method may not work correctly.

If your USB controller is in sys-usb then running Xfburn or Brasero there
is the best option. If not, and you have several USB controllers, you might
want to investigate creating a sys-usb for that purpose. Otherwise then you
may need to decide if you want to install a DvD burning package directly in
dom0, which generally should be avoided if possible.

Steve


On Tue, Nov 24, 2020 at 2:26 PM Shawn Creighton  wrote:

> Trying to create a bootable usb, installed Xfburn and connected the usb to
> the AppVM but when I open Xfburn as root it doesn't see the usb and says:
>
> "no burners currently available, possibly the discs are in use and cannot
> get accessed"
>
> Also tried installing Brasero which won't burn to usb
>
> --
> 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/9d137cef-525f-48bf-bd49-85c17ad02b9an%40googlegroups.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/CAJ5FDnjkOTrXf0c%3DMzwV_5u_e%3DrqK5ASNCDTY2jUNKU0eeQfwg%40mail.gmail.com.

[qubes-users] Xfburn not seeing usb

[Shawn Creighton]

Trying to create a bootable usb, installed Xfburn and connected the usb to 
the AppVM but when I open Xfburn as root it doesn't see the usb and says:

"no burners currently available, possibly the discs are in use and cannot 
get accessed"

Also tried installing Brasero which won't burn to usb 

-- 
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/9d137cef-525f-48bf-bd49-85c17ad02b9an%40googlegroups.com.

[qubes-users] HCL - HP Probook 640 G3

[Effie ML]

Hello Qubes Users.

Here is my HCL from my HP Probook 640 G3.

Regards.

Effie ML.



--
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/4115888f-1917-b57c-1bf2-85b2373ace84%40encryptionin.space.


Qubes-HCL-Hewlett_Packard-HP_Pavilion_Notebook_-20201123-171313.yml
Description: application/yaml

[qubes-users] Fedora 31 has reached EOL

[Andrew David Wong]

Dear Qubes Community,

Fedora 31 has reached EOL (end-of-life [1]). If you have not already 
done so, we strongly recommend upgrading your Fedora 31 TemplateVMs and 
StandaloneVMs to Fedora 32 immediately. We provide step-by-step upgrade 
instructions for upgrading Fedora TemplateVMs [2]. For a complete list 
of TemplateVM versions supported for your specific version of Qubes, see 
the list of supported TemplateVM versions [3].


We also provide a fresh Fedora 32 TemplateVM package through the 
official Qubes repositories, which you can install in dom0 by following 
the standard installation instructions [4].


After upgrading your TemplateVMs, please remember to switch all qubes 
that were using the old template to use the new one [5].


Please note that no user action is required regarding the OS version in 
dom0. For details, please see our note on dom0 and EOL [6].



[1] https://fedoraproject.org/wiki/End_of_life
[2] https://www.qubes-os.org/doc/template/fedora/upgrade/
[3] https://www.qubes-os.org/doc/supported-versions/#templatevms
[4] https://www.qubes-os.org/doc/templates/fedora/#installing
[5] https://www.qubes-os.org/doc/templates/#switching
[6] https://www.qubes-os.org/doc/supported-versions/#note-on-dom0-and-eol

This announcement is also available on the Qubes website:
https://www.qubes-os.org/news/2020/11/24/fedora-31-eol/

--
Andrew David Wong (Axon)
Community Manager, Qubes OS
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/b47555fd-0f24-63b6-f006-d8305739c72d%40qubes-os.org.


OpenPGP_signature
Description: OpenPGP digital signature

[qubes-users] QSB #062: Stack corruption from XSA-346 change (XSA-355)

[Andrew David Wong]

Dear Qubes Community,

We have just published Qubes Security Bulletin (QSB) #062: Stack 
corruption from XSA-346 change (XSA-355). 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 #062 in the qubes-secpack:

https://github.com/QubesOS/qubes-secpack/blob/master/QSBs/qsb-062-2020.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/

View XSA-355 in the XSA Tracker:

https://www.qubes-os.org/security/xsa/#355

```


 ---===[ Qubes Security Bulletin #62 ]===---

 2020-11-24


   Stack corruption from XSA-346 change (XSA-355)


Summary


On 2020-11-24, the Xen Security Team published Xen Security Advisory
355 (XSA-355) [1] with the following description:

| One of the two changes for XSA-346 introduced an on-stack array.  The
| check for guarding against overrunning this array was off by one,
| allowing for corruption of the first stack slot immediately following
| this array.
|
| A malicious or buggy HVM or PVH guest can cause Xen to crash, resulting
| in a Denial of Service (DoS) to the entire host.  Privilege escalation
| as well as information leaks cannot be excluded.


Patching
=

The specific packages that resolve the problems discussed in this
bulletin are as follows:

  For Qubes 4.0:
  - Xen packages, version 4.8.5-27
  For Qubes 4.1:
  - Xen packages, version 4.14.0-8

The packages are to be installed in dom0 via the Qube Manager or via
the qubes-dom0-update command as follows:

  For updates from the stable repository (not immediately available):
  $ sudo qubes-dom0-update

  For updates from the security-testing repository:
  $ sudo qubes-dom0-update --enablerepo=qubes-dom0-security-testing

A system restart will be required afterwards.

These packages will migrate from the security-testing repository to the
current (stable) repository over the next two weeks after being tested
by the community.

If you use Anti Evil Maid, you will need to reseal your secret
passphrase to new PCR values, as PCR18+19 will change due to the new
Xen binaries.


Credits


See the original Xen Security Advisory.


References
===

[1] https://xenbits.xen.org/xsa/advisory-355.html

--
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/2020/11/24/qsb-062/

--
Andrew David Wong (Axon)
Community Manager, Qubes OS
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/46f8bae9-5540-ff20-079a-930016e146a3%40qubes-os.org.


OpenPGP_signature
Description: OpenPGP digital signature