gpg: key B6A0BB95CA74A5C3: public key "Joanna Rutkowska (Qubes Documentation Signing Key)" imported
gpg: key F32894BE9684938A: public key "Marek Marczykowski-Górecki (Qubes Documentation Signing Key)" imported
gpg: key 6E7A27B909DAFB92: public key "Hakisho Nukama (Qubes Documentation Signing Key)" imported
gpg: key 485C7504F27D0A72: 1 signature not checked due to a missing key
gpg: key 485C7504F27D0A72: public key "Sven Semmler (Qubes Documentation Signing Key)" imported
gpg: key BB52274595B71262: public key "unman (Qubes Documentation Signing Key)" imported
gpg: key DC2F3678D272F2A8: 1 signature not checked due to a missing key
gpg: key DC2F3678D272F2A8: public key "Wojtek Porczyk (Qubes OS documentation signing key)" imported
gpg: key FD64F4F9E9720C4D: 1 signature not checked due to a missing key
gpg: key FD64F4F9E9720C4D: public key "Zrubi (Qubes Documentation Signing Key)" imported
gpg: key DDFA1A3E36879494: "Qubes Master Signing Key" not changed
gpg: key 1848792F9E2795E9: public key "Qubes OS Release 4 Signing Key" imported
gpg: qubes-secpack/keys/release-keys/retired: read error: Is a directory
gpg: no valid OpenPGP data found.
gpg: key D655A4F21830E06A: public key "Marek Marczykowski-Górecki (Qubes security pack)" imported
gpg: key ACC2602F3F48CB21: public key "Qubes OS Security Team" imported
gpg: qubes-secpack/keys/security-team/retired: read error: Is a directory
gpg: no valid OpenPGP data found.
gpg: key 4AC18DE1112E1490: public key "Simon Gaiser (Qubes Security Pack signing key)" imported
gpg: Total number processed: 17
gpg: imported: 16
gpg: unchanged: 1
gpg: marginals needed: 3 completes needed: 1 trust model: pgp
gpg: depth: 0 valid: 1 signed: 6 trust: 0-, 0q, 0n, 0m, 0f, 1u
gpg: depth: 1 valid: 6 signed: 0 trust: 6-, 0q, 0n, 0m, 0f, 0u
Verify signed Git tags.
$ cd qubes-secpack/
$ git tag -v `git describe`
object 266e14a6fae57c9a91362c9ac784d3a891f4d351
type commit
tag marmarek_sec_266e14a6
tagger Marek Marczykowski-Górecki 1677757924 +0100
Tag for commit 266e14a6fae57c9a91362c9ac784d3a891f4d351
gpg: Signature made Thu 02 Mar 2023 03:52:04 AM PST
gpg: using RSA key 2D1771FE4D767EDC76B089FAD655A4F21830E06A
gpg: Good signature from "Marek Marczykowski-Górecki (Qubes security pack)" [full]
The exact output will differ, but the final line should always start with gpg: Good signature from... followed by an appropriate key. The [full] indicates full trust, which this key inherits in virtue of being validly signed by the QMSK.
Verify PGP signatures, e.g.:
$ cd QSBs/
$ gpg --verify qsb-087-2022.txt.sig.marmarek qsb-087-2022.txt
gpg: Signature made Wed 23 Nov 2022 04:05:51 AM PST
gpg: using RSA key 2D1771FE4D767EDC76B089FAD655A4F21830E06A
gpg: Good signature from "Marek Marczykowski-Górecki (Qubes security pack)" [full]
$ gpg --verify qsb-087-2022.txt.sig.simon qsb-087-2022.txt
gpg: Signature made Wed 23 Nov 2022 03:50:42 AM PST
gpg: using RSA key EA18E7F040C41DDAEFE9AA0F4AC18DE1112E1490
gpg: Good signature from "Simon Gaiser (Qubes Security Pack signing key)" [full]
$ cd ../canaries/
$ gpg --verify canary-034-2023.txt.sig.marmarek canary-034-2023.txt
gpg: Signature made Thu 02 Mar 2023 03:51:48 AM PST
gpg: using RSA key 2D1771FE4D767EDC76B089FAD655A4F21830E06A
gpg: Good signature from "Marek Marczykowski-Górecki (Qubes security pack)" [full]
$ gpg --verify canary-034-2023.txt.sig.simon canary-034-2023.txt
gpg: Signature made Thu 02 Mar 2023 01:47:52 AM PST
gpg: using RSA key EA18E7F040C41DDAEFE9AA0F4AC18DE1112E1490
gpg: Good signature from "Simon Gaiser (Qubes Security Pack signing key)" [full]
Again, the exact output will differ, but the final line of output from each gpg --verify command should always start with gpg: Good signature from... followed by an appropriate key.
For this announcement (QSB-094), the commands are:
gpg: key F32894BE9684938A: public key "Marek Marczykowski-Górecki (Qubes Documentation Signing Key)" imported
gpg: key 6E7A27B909DAFB92: public key "Hakisho Nukama (Qubes Documentation Signing Key)" imported
gpg: key 485C7504F27D0A72: 1 signature not checked due to a missing key
gpg: key 485C7504F27D0A72: public key "Sven Semmler (Qubes Documentation Signing Key)" imported
gpg: key BB52274595B71262: public key "unman (Qubes Documentation Signing Key)" imported
gpg: key DC2F3678D272F2A8: 1 signature not checked due to a missing key
gpg: key DC2F3678D272F2A8: public key "Wojtek Porczyk (Qubes OS documentation signing key)" imported
gpg: key FD64F4F9E9720C4D: 1 signature not checked due to a missing key
gpg: key FD64F4F9E9720C4D: public key "Zrubi (Qubes Documentation Signing Key)" imported
gpg: key DDFA1A3E36879494: "Qubes Master Signing Key" not changed
gpg: key 1848792F9E2795E9: public key "Qubes OS Release 4 Signing Key" imported
gpg: qubes-secpack/keys/release-keys/retired: read error: Is a directory
gpg: no valid OpenPGP data found.
gpg: key D655A4F21830E06A: public key "Marek Marczykowski-Górecki (Qubes security pack)" imported
gpg: key ACC2602F3F48CB21: public key "Qubes OS Security Team" imported
gpg: qubes-secpack/keys/security-team/retired: read error: Is a directory
gpg: no valid OpenPGP data found.
gpg: key 4AC18DE1112E1490: public key "Simon Gaiser (Qubes Security Pack signing key)" imported
gpg: Total number processed: 17
gpg: imported: 16
gpg: unchanged: 1
gpg: marginals needed: 3 completes needed: 1 trust model: pgp
gpg: depth: 0 valid: 1 signed: 6 trust: 0-, 0q, 0n, 0m, 0f, 1u
gpg: depth: 1 valid: 6 signed: 0 trust: 6-, 0q, 0n, 0m, 0f, 0u
Verify signed Git tags.
$ cd qubes-secpack/
$ git tag -v `git describe`
object 266e14a6fae57c9a91362c9ac784d3a891f4d351
type commit
tag marmarek_sec_266e14a6
tagger Marek Marczykowski-Górecki 1677757924 +0100
Tag for commit 266e14a6fae57c9a91362c9ac784d3a891f4d351
gpg: Signature made Thu 02 Mar 2023 03:52:04 AM PST
gpg: using RSA key 2D1771FE4D767EDC76B089FAD655A4F21830E06A
gpg: Good signature from "Marek Marczykowski-Górecki (Qubes security pack)" [full]
The exact output will differ, but the final line should always start with gpg: Good signature from... followed by an appropriate key. The [full] indicates full trust, which this key inherits in virtue of being validly signed by the QMSK.
Verify PGP signatures, e.g.:
$ cd QSBs/
$ gpg --verify qsb-087-2022.txt.sig.marmarek qsb-087-2022.txt
gpg: Signature made Wed 23 Nov 2022 04:05:51 AM PST
gpg: using RSA key 2D1771FE4D767EDC76B089FAD655A4F21830E06A
gpg: Good signature from "Marek Marczykowski-Górecki (Qubes security pack)" [full]
$ gpg --verify qsb-087-2022.txt.sig.simon qsb-087-2022.txt
gpg: Signature made Wed 23 Nov 2022 03:50:42 AM PST
gpg: using RSA key EA18E7F040C41DDAEFE9AA0F4AC18DE1112E1490
gpg: Good signature from "Simon Gaiser (Qubes Security Pack signing key)" [full]
$ cd ../canaries/
$ gpg --verify canary-034-2023.txt.sig.marmarek canary-034-2023.txt
gpg: Signature made Thu 02 Mar 2023 03:51:48 AM PST
gpg: using RSA key 2D1771FE4D767EDC76B089FAD655A4F21830E06A
gpg: Good signature from "Marek Marczykowski-Górecki (Qubes security pack)" [full]
$ gpg --verify canary-034-2023.txt.sig.simon canary-034-2023.txt
gpg: Signature made Thu 02 Mar 2023 01:47:52 AM PST
gpg: using RSA key EA18E7F040C41DDAEFE9AA0F4AC18DE1112E1490
gpg: Good signature from "Simon Gaiser (Qubes Security Pack signing key)" [full]
Again, the exact output will differ, but the final line of output from each gpg --verify command should always start with gpg: Good signature from... followed by an appropriate key.
For this announcement (QSB-094), the commands are:
$ gpg --verify qsb-094-2023.txt.sig.marmarek qsb-094-2023.txt
$ gpg --verify qsb-094-2023.txt.sig.simon qsb-094-2023.txt
You can also verify the signatures directly from this announcement in addition to or instead of verifying the files from the qubes-secpack. Simply copy and paste the QSB-094 text into a plain text file and do the same for both signature files. Then, perform the same authentication steps as listed above, substituting the filenames above with the names of the files you just created.
$ gpg --verify qsb-094-2023.txt.sig.simon qsb-094-2023.txt
You can also verify the signatures directly from this announcement in addition to or instead of verifying the files from the qubes-secpack. Simply copy and paste the QSB-094 text into a plain text file and do the same for both signature files. Then, perform the same authentication steps as listed above, substituting the filenames above with the names of the files you just created.
XSAs released on 2023-10-10
https://www.qubes-os.org/news/2023/10/10/xsas-released-on-2023-10-10/
The Xen Project (https://xenproject.org/) has released one or more Xen security advisories (XSAs) (https://xenbits.xen.org/xsa/).
The security of Qubes OS is affected.
Therefore, user action is required.
XSAs that DO affect the security of Qubes OS
The following XSAs do affect the security of Qubes OS:
XSA-442 (https://xenbits.xen.org/xsa/advisory-442.html)
Please see QSB-095 (https://www.qubes-os.org/news/2023/10/10/qsb-095/) for details.
XSAs that DO NOT affect the security of Qubes OS
The following XSAs do not affect the security of Qubes OS, and no user action is necessary:
XSA-440 (https://xenbits.xen.org/xsa/advisory-440.html)
Denial of service (DoS) only
XSA-441 (https://xenbits.xen.org/xsa/advisory-441.html)
Denial of service (DoS) only
XSA-443 (https://xenbits.xen.org/xsa/advisory-443.html)
Qubes OS does not use pygrub.
XSA-444 (https://xenbits.xen.org/xsa/advisory-444.html)
Denial of service (DoS) only
About this announcement
Qubes OS uses the Xen hypervisor (https://wiki.xenproject.org/wiki/Xen_Project_Software_Overview) as part of its architecture (https://www.qubes-os.org/doc/architecture/). When the Xen Project (https://xenproject.org/) publicly discloses a vulnerability in the Xen hypervisor, they issue a notice called a Xen security advisory (XSA) (https://xenproject.org/developers/security-policy/). Vulnerabilities in the Xen hypervisor sometimes have security implications for Qubes OS. When they do, we issue a notice called a Qubes security bulletin (QSB) (https://www.qubes-os.org/security/qsb/). (QSBs are also issued for non-Xen vulnerabilities.) However, QSBs can provide only positive confirmation that certain XSAs do affect the security of Qubes OS. QSBs cannot provide negative confirmation that other XSAs do not affect the security of Qubes OS. Therefore, we also maintain an XSA tracker (https://www.qubes-os.org/security/xsa/), which is a comprehensive list of all XSAs publicly disclosed to date, including whether each one affects the security of Qubes OS. When new XSAs are published, we add them to the XSA tracker and publish a notice like this one in order to inform Qubes users that a new batch of XSAs has been released and whether each one affects the security of Qubes OS.
https://www.qubes-os.org/news/2023/10/10/xsas-released-on-2023-10-10/
The Xen Project (https://xenproject.org/) has released one or more Xen security advisories (XSAs) (https://xenbits.xen.org/xsa/).
The security of Qubes OS is affected.
Therefore, user action is required.
XSAs that DO affect the security of Qubes OS
The following XSAs do affect the security of Qubes OS:
XSA-442 (https://xenbits.xen.org/xsa/advisory-442.html)
Please see QSB-095 (https://www.qubes-os.org/news/2023/10/10/qsb-095/) for details.
XSAs that DO NOT affect the security of Qubes OS
The following XSAs do not affect the security of Qubes OS, and no user action is necessary:
XSA-440 (https://xenbits.xen.org/xsa/advisory-440.html)
Denial of service (DoS) only
XSA-441 (https://xenbits.xen.org/xsa/advisory-441.html)
Denial of service (DoS) only
XSA-443 (https://xenbits.xen.org/xsa/advisory-443.html)
Qubes OS does not use pygrub.
XSA-444 (https://xenbits.xen.org/xsa/advisory-444.html)
Denial of service (DoS) only
About this announcement
Qubes OS uses the Xen hypervisor (https://wiki.xenproject.org/wiki/Xen_Project_Software_Overview) as part of its architecture (https://www.qubes-os.org/doc/architecture/). When the Xen Project (https://xenproject.org/) publicly discloses a vulnerability in the Xen hypervisor, they issue a notice called a Xen security advisory (XSA) (https://xenproject.org/developers/security-policy/). Vulnerabilities in the Xen hypervisor sometimes have security implications for Qubes OS. When they do, we issue a notice called a Qubes security bulletin (QSB) (https://www.qubes-os.org/security/qsb/). (QSBs are also issued for non-Xen vulnerabilities.) However, QSBs can provide only positive confirmation that certain XSAs do affect the security of Qubes OS. QSBs cannot provide negative confirmation that other XSAs do not affect the security of Qubes OS. Therefore, we also maintain an XSA tracker (https://www.qubes-os.org/security/xsa/), which is a comprehensive list of all XSAs publicly disclosed to date, including whether each one affects the security of Qubes OS. When new XSAs are published, we add them to the XSA tracker and publish a notice like this one in order to inform Qubes users that a new batch of XSAs has been released and whether each one affects the security of Qubes OS.
QSB-095: Missing IOMMU TLB flushing on x86 AMD systems
https://www.qubes-os.org/news/2023/10/10/qsb-095/
We have published Qubes Security Bulletin 095: Missing IOMMU TLB flushing on x86 AMD systems (https://github.com/QubesOS/qubes-secpack/blob/main/QSBs/qsb-095-2023.txt). The text of this QSB and its accompanying cryptographic signatures are reproduced below. For an explanation of this announcement and instructions for authenticating this QSB, please see the end of this announcement.
Qubes Security Bulletin 095
---===[ Qubes Security Bulletin 095 ]===---
2023-10-10
Missing IOMMU TLB flushing on x86 AMD systems
User action
------------
Continue to update normally [1] in order to receive the security updates
described in the "Patching" section below. No other user action is required in
response to this QSB.
Summary
--------
On 2023-10-10, the Xen Project published XSA-442, "x86/AMD: missing
IOMMU TLB flushing" [3]:
| The caching invalidation guidelines from the AMD-Vi specification (48882—Rev
| 3.07-PUB—Oct 2022) is incorrect on some hardware, as devices will malfunction
| (see stale DMA mappings) if some fields of the DTE are updated but the IOMMU
| TLB is not flushed.
|
| Such stale DMA mappings can point to memory ranges not owned by the guest,
| thus allowing access to unindented memory regions.
Impact
-------
On affected systems, an attacker who compromises a qube with access to a PCI
device could attempt to exploit this vulnerability in order to escalate the
attacker's privileges, perform a denial-of-service (DoS) attack against the
host, and leak information. In the default Qubes OS configuration, the qubes
that have access to PCI devices are sys-net and sys-usb.
Affected systems
-----------------
Only x86 AMD systems are vulnerable.
Patching
---------
The following packages contain security updates that address the
vulnerabilities described in this bulletin:
For Qubes 4.1, in dom0:
- Xen packages, version 4.14.6-3
For Qubes 4.2, in dom0:
- Xen packages, version 4.17.2-3
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. [2] Once available, the packages are to be installed
via the Qubes Update tool or its command-line equivalents. [1]
Dom0 must be restarted afterward in order for the updates to take
effect.
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://www.qubes-os.org/doc/how-to-update/
[2] https://www.qubes-os.org/doc/testing/
[3] https://xenbits.xen.org/xsa/advisory-442.html
--
The Qubes Security Team
https://www.qubes-os.org/security/
Source: https://github.com/QubesOS/qubes-secpack/blob/main/QSBs/qsb-095-2023.txt
Marek Marczykowski-Górecki (https://www.qubes-os.org/team/#marek-marczykowski-g%C3%B3recki)’s PGP signature
-----BEGIN PGP SIGNATURE-----
iQIzBAABCAAdFiEELRdx/k12ftx2sIn61lWk8hgw4GoFAmUlOMwACgkQ1lWk8hgw
4GoyoxAAlgmOduZt8/CYSBEO0HaXgP7NmDx+8qYs6RE6Vk3b9FvTyGrNMowT7I4a
Sjr2SDNgf/a97dzMnEL3uAmAt2OGn1dKOKdlPVFmkwz9Pu4/MPFl153n4p7FwLEq
Iy+Y/4Habps/iZ+rzEnIXTwjFnL6H38i5GnkV0DmEtVU3lljLWv/B8eFsDZzuK52
FldpGe2B6Ks21dG76zTxffqAX4tEmHSIO7x4Vjk1RWxum4pEWTEvtfD1Olc3yv4C
qF0A5B7PxMs4CumZW2P+/xS4uEZW4IGZ9o8Nhqj35tIkSV8tmeyRAL3hRgcHxc5s
5bJyg+wAvYztW6aUTbShpzag/nu/kVWFjbgJYTZyw016vhvkWjLa3OiQxkufxp+X
3jK4rBn7RxBLBtOlEWZdy7tMC8bSNUNG5p8MN1uiWOH83+XgpObv4IJwiF0W2sEb
BOe0T+Nsny3LoMtdwP5fxTdZijyE4HX9nCRpJmX+IuD2+3OAiio0BAEoV/e/6d/z
sFcdAugJs8xmiFUkNwKmFpIGcGgievffp3IRukMh6YsKGYb4iA3LrL1IEtcy+eaR
tILQHOLL2wmH1Vb35PgHmliE9ApWqh5DoziYejQ1gW/Ql2IEtTx+zNeBWbgGS+e9
D0m0aN+lXsC/a0/arEYzuCnK+1t6tBk65qsUy/K4n/uXzJYEiVk=
=NYhK
-----END PGP SIGNATURE-----
https://www.qubes-os.org/news/2023/10/10/qsb-095/
We have published Qubes Security Bulletin 095: Missing IOMMU TLB flushing on x86 AMD systems (https://github.com/QubesOS/qubes-secpack/blob/main/QSBs/qsb-095-2023.txt). The text of this QSB and its accompanying cryptographic signatures are reproduced below. For an explanation of this announcement and instructions for authenticating this QSB, please see the end of this announcement.
Qubes Security Bulletin 095
---===[ Qubes Security Bulletin 095 ]===---
2023-10-10
Missing IOMMU TLB flushing on x86 AMD systems
User action
------------
Continue to update normally [1] in order to receive the security updates
described in the "Patching" section below. No other user action is required in
response to this QSB.
Summary
--------
On 2023-10-10, the Xen Project published XSA-442, "x86/AMD: missing
IOMMU TLB flushing" [3]:
| The caching invalidation guidelines from the AMD-Vi specification (48882—Rev
| 3.07-PUB—Oct 2022) is incorrect on some hardware, as devices will malfunction
| (see stale DMA mappings) if some fields of the DTE are updated but the IOMMU
| TLB is not flushed.
|
| Such stale DMA mappings can point to memory ranges not owned by the guest,
| thus allowing access to unindented memory regions.
Impact
-------
On affected systems, an attacker who compromises a qube with access to a PCI
device could attempt to exploit this vulnerability in order to escalate the
attacker's privileges, perform a denial-of-service (DoS) attack against the
host, and leak information. In the default Qubes OS configuration, the qubes
that have access to PCI devices are sys-net and sys-usb.
Affected systems
-----------------
Only x86 AMD systems are vulnerable.
Patching
---------
The following packages contain security updates that address the
vulnerabilities described in this bulletin:
For Qubes 4.1, in dom0:
- Xen packages, version 4.14.6-3
For Qubes 4.2, in dom0:
- Xen packages, version 4.17.2-3
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. [2] Once available, the packages are to be installed
via the Qubes Update tool or its command-line equivalents. [1]
Dom0 must be restarted afterward in order for the updates to take
effect.
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://www.qubes-os.org/doc/how-to-update/
[2] https://www.qubes-os.org/doc/testing/
[3] https://xenbits.xen.org/xsa/advisory-442.html
--
The Qubes Security Team
https://www.qubes-os.org/security/
Source: https://github.com/QubesOS/qubes-secpack/blob/main/QSBs/qsb-095-2023.txt
Marek Marczykowski-Górecki (https://www.qubes-os.org/team/#marek-marczykowski-g%C3%B3recki)’s PGP signature
-----BEGIN PGP SIGNATURE-----
iQIzBAABCAAdFiEELRdx/k12ftx2sIn61lWk8hgw4GoFAmUlOMwACgkQ1lWk8hgw
4GoyoxAAlgmOduZt8/CYSBEO0HaXgP7NmDx+8qYs6RE6Vk3b9FvTyGrNMowT7I4a
Sjr2SDNgf/a97dzMnEL3uAmAt2OGn1dKOKdlPVFmkwz9Pu4/MPFl153n4p7FwLEq
Iy+Y/4Habps/iZ+rzEnIXTwjFnL6H38i5GnkV0DmEtVU3lljLWv/B8eFsDZzuK52
FldpGe2B6Ks21dG76zTxffqAX4tEmHSIO7x4Vjk1RWxum4pEWTEvtfD1Olc3yv4C
qF0A5B7PxMs4CumZW2P+/xS4uEZW4IGZ9o8Nhqj35tIkSV8tmeyRAL3hRgcHxc5s
5bJyg+wAvYztW6aUTbShpzag/nu/kVWFjbgJYTZyw016vhvkWjLa3OiQxkufxp+X
3jK4rBn7RxBLBtOlEWZdy7tMC8bSNUNG5p8MN1uiWOH83+XgpObv4IJwiF0W2sEb
BOe0T+Nsny3LoMtdwP5fxTdZijyE4HX9nCRpJmX+IuD2+3OAiio0BAEoV/e/6d/z
sFcdAugJs8xmiFUkNwKmFpIGcGgievffp3IRukMh6YsKGYb4iA3LrL1IEtcy+eaR
tILQHOLL2wmH1Vb35PgHmliE9ApWqh5DoziYejQ1gW/Ql2IEtTx+zNeBWbgGS+e9
D0m0aN+lXsC/a0/arEYzuCnK+1t6tBk65qsUy/K4n/uXzJYEiVk=
=NYhK
-----END PGP SIGNATURE-----
Source: https://github.com/QubesOS/qubes-secpack/blob/main/QSBs/qsb-095-2023.txt.sig.marmarek
Simon Gaiser (aka HW42) (https://www.qubes-os.org/team/#simon-gaiser-aka-hw42)’s PGP signature
-----BEGIN PGP SIGNATURE-----
iQIzBAABCgAdFiEE6hjn8EDEHdrv6aoPSsGN4REuFJAFAmUlM3cACgkQSsGN4REu
FJB8SA/+M1B96X+3C+2QBJW9q8h3cLuMVfMjlD9lRqESi/AXduNZN/o29WISw85z
6S+gTOqdVPf6ggfc+r4XxY3h1KICw/G9V8WwV8FPVqJVXjapnkTtqJ4drMu8v2vb
Di9G200bAngslFdxskAYQ73ZUTIyw7f6ljUHBH16c9dB43RvfqBAN6XWb/M745Am
vS005JvermS7TXMN6BemcIhKrMP+QLeMf+kVYJt18LGKHJX3TmY6Z9On7csyRgxL
8xEEYPBjjthpyF0Wy/h+9XTeQKhdaMHX7h+h3A8FAK4ZlfdFknrdJ6or6xjHyqv7
rfRdQMtBXGb6YQRJlWjRnKd1BnwCHXg6Y487M1Keed8OX7g6yVfEjlbo30vCFRoo
UK8/DMukhA+f+1VDyLMpAIvCjNwaVQjFrTC1LVDf6YskqgJROKHVFv9Ed+IJinQf
T8Bb8xk82fh6AgsFZQ4+Vl67BLFs5JGLeEg5xJtcIhiuV+AZs+6F21YCfwsuUWuW
fC0QtEctzET+BhMr5SyrqicMpSw1JRnfCZjjaDed/noEliwG2cS6VarbOCTqcXGH
5HJaYB7b9lYDG2DICBAMN9vukN0O05JmqtLULVhmai3gH3cA3OFSTbbKUqGvNXde
BS9Exs7T1osXcarI+ZAb5xxJanhrRwX4bYffAJd45vQwKekf/+w=
=Sojp
-----END PGP SIGNATURE-----
Source: https://github.com/QubesOS/qubes-secpack/blob/main/QSBs/qsb-095-2023.txt.sig.simon
What is the purpose of this announcement?
The purpose of this announcement is to inform the Qubes community that a new Qubes security bulletin (QSB) has been published.
What is a Qubes security bulletin (QSB)?
A Qubes security bulletin (QSB) is a security announcement issued by the Qubes security team (https://www.qubes-os.org/security/#qubes-security-team). A QSB typically provides a summary and impact analysis of one or more recently-discovered software vulnerabilities, including details about patching to address them. For a list of all QSBs, see Qubes security bulletins (QSBs) (https://www.qubes-os.org/security/qsb/).
Why should I care about QSBs?
QSBs tell you what actions you must take in order to protect yourself from recently-discovered security vulnerabilities. In most cases, security vulnerabilities are addressed by updating normally (https://www.qubes-os.org/doc/how-to-update/). However, in some cases, special user action is required. In all cases, the required actions are detailed in QSBs.
What are the PGP signatures that accompany QSBs?
A PGP (https://en.wikipedia.org/wiki/Pretty_Good_Privacy) signature is a cryptographic digital signature (https://en.wikipedia.org/wiki/Digital_signature) made in accordance with the OpenPGP (https://en.wikipedia.org/wiki/Pretty_Good_Privacy#OpenPGP) standard. PGP signatures can be cryptographically verified with programs like GNU Privacy Guard (GPG) (https://gnupg.org/). The Qubes security team cryptographically signs all QSBs so that Qubes users have a reliable way to check whether QSBs are genuine. The only way to be certain that a QSB is authentic is by verifying its PGP signatures.
Why should I care whether a QSB is authentic?
A forged QSB could deceive you into taking actions that adversely affect the security of your Qubes OS system, such as installing malware or making configuration changes that render your system vulnerable to attack. Falsified QSBs could sow fear, uncertainty, and doubt about the security of Qubes OS or the status of the Qubes OS Project.
How do I verify the PGP signatures on a QSB?
The following command-line instructions assume a Linux system with git and gpg installed. (For Windows and Mac options, see OpenPGP software (https://www.qubes-os.org/security/verifying-signatures/#openpgp-software).)
Obtain the Qubes Master Signing Key (QMSK), e.g.:
$ gpg --fetch-keys https://keys.qubes-os.org/keys/qubes-master-signing-key.asc
gpg: directory '/home/user/.gnupg' created
gpg: keybox '/home/user/.gnupg/pubring.kbx' created
gpg: requesting key from 'https://keys.qubes-os.org/keys/qubes-master-signing-key.asc'
gpg: /home/user/.gnupg/trustdb.gpg: trustdb created
gpg: key DDFA1A3E36879494: public key "Qubes Master Signing Key" imported
gpg: Total number processed: 1
gpg: imported: 1
Simon Gaiser (aka HW42) (https://www.qubes-os.org/team/#simon-gaiser-aka-hw42)’s PGP signature
-----BEGIN PGP SIGNATURE-----
iQIzBAABCgAdFiEE6hjn8EDEHdrv6aoPSsGN4REuFJAFAmUlM3cACgkQSsGN4REu
FJB8SA/+M1B96X+3C+2QBJW9q8h3cLuMVfMjlD9lRqESi/AXduNZN/o29WISw85z
6S+gTOqdVPf6ggfc+r4XxY3h1KICw/G9V8WwV8FPVqJVXjapnkTtqJ4drMu8v2vb
Di9G200bAngslFdxskAYQ73ZUTIyw7f6ljUHBH16c9dB43RvfqBAN6XWb/M745Am
vS005JvermS7TXMN6BemcIhKrMP+QLeMf+kVYJt18LGKHJX3TmY6Z9On7csyRgxL
8xEEYPBjjthpyF0Wy/h+9XTeQKhdaMHX7h+h3A8FAK4ZlfdFknrdJ6or6xjHyqv7
rfRdQMtBXGb6YQRJlWjRnKd1BnwCHXg6Y487M1Keed8OX7g6yVfEjlbo30vCFRoo
UK8/DMukhA+f+1VDyLMpAIvCjNwaVQjFrTC1LVDf6YskqgJROKHVFv9Ed+IJinQf
T8Bb8xk82fh6AgsFZQ4+Vl67BLFs5JGLeEg5xJtcIhiuV+AZs+6F21YCfwsuUWuW
fC0QtEctzET+BhMr5SyrqicMpSw1JRnfCZjjaDed/noEliwG2cS6VarbOCTqcXGH
5HJaYB7b9lYDG2DICBAMN9vukN0O05JmqtLULVhmai3gH3cA3OFSTbbKUqGvNXde
BS9Exs7T1osXcarI+ZAb5xxJanhrRwX4bYffAJd45vQwKekf/+w=
=Sojp
-----END PGP SIGNATURE-----
Source: https://github.com/QubesOS/qubes-secpack/blob/main/QSBs/qsb-095-2023.txt.sig.simon
What is the purpose of this announcement?
The purpose of this announcement is to inform the Qubes community that a new Qubes security bulletin (QSB) has been published.
What is a Qubes security bulletin (QSB)?
A Qubes security bulletin (QSB) is a security announcement issued by the Qubes security team (https://www.qubes-os.org/security/#qubes-security-team). A QSB typically provides a summary and impact analysis of one or more recently-discovered software vulnerabilities, including details about patching to address them. For a list of all QSBs, see Qubes security bulletins (QSBs) (https://www.qubes-os.org/security/qsb/).
Why should I care about QSBs?
QSBs tell you what actions you must take in order to protect yourself from recently-discovered security vulnerabilities. In most cases, security vulnerabilities are addressed by updating normally (https://www.qubes-os.org/doc/how-to-update/). However, in some cases, special user action is required. In all cases, the required actions are detailed in QSBs.
What are the PGP signatures that accompany QSBs?
A PGP (https://en.wikipedia.org/wiki/Pretty_Good_Privacy) signature is a cryptographic digital signature (https://en.wikipedia.org/wiki/Digital_signature) made in accordance with the OpenPGP (https://en.wikipedia.org/wiki/Pretty_Good_Privacy#OpenPGP) standard. PGP signatures can be cryptographically verified with programs like GNU Privacy Guard (GPG) (https://gnupg.org/). The Qubes security team cryptographically signs all QSBs so that Qubes users have a reliable way to check whether QSBs are genuine. The only way to be certain that a QSB is authentic is by verifying its PGP signatures.
Why should I care whether a QSB is authentic?
A forged QSB could deceive you into taking actions that adversely affect the security of your Qubes OS system, such as installing malware or making configuration changes that render your system vulnerable to attack. Falsified QSBs could sow fear, uncertainty, and doubt about the security of Qubes OS or the status of the Qubes OS Project.
How do I verify the PGP signatures on a QSB?
The following command-line instructions assume a Linux system with git and gpg installed. (For Windows and Mac options, see OpenPGP software (https://www.qubes-os.org/security/verifying-signatures/#openpgp-software).)
Obtain the Qubes Master Signing Key (QMSK), e.g.:
$ gpg --fetch-keys https://keys.qubes-os.org/keys/qubes-master-signing-key.asc
gpg: directory '/home/user/.gnupg' created
gpg: keybox '/home/user/.gnupg/pubring.kbx' created
gpg: requesting key from 'https://keys.qubes-os.org/keys/qubes-master-signing-key.asc'
gpg: /home/user/.gnupg/trustdb.gpg: trustdb created
gpg: key DDFA1A3E36879494: public key "Qubes Master Signing Key" imported
gpg: Total number processed: 1
gpg: imported: 1
(For more ways to obtain the QMSK, see How to import and authenticate the Qubes Master Signing Key (https://www.qubes-os.org/security/verifying-signatures/#how-to-import-and-authenticate-the-qubes-master-signing-key).)
View the fingerprint of the PGP key you just imported. (Note: gpg> indicates a prompt inside of the GnuPG program. Type what appears after it when prompted.)
$ gpg --edit-key 0x427F11FD0FAA4B080123F01CDDFA1A3E36879494
gpg (GnuPG) 2.2.27; Copyright (C) 2021 Free Software Foundation, Inc.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
pub rsa4096/DDFA1A3E36879494
created: 2010-04-01 expires: never usage: SC
trust: unknown validity: unknown
[ unknown] (1). Qubes Master Signing Key
gpg> fpr
pub rsa4096/DDFA1A3E36879494 2010-04-01 Qubes Master Signing Key
Primary key fingerprint: 427F 11FD 0FAA 4B08 0123 F01C DDFA 1A3E 3687 9494
Important: At this point, you still don’t know whether the key you just imported is the genuine QMSK or a forgery. In order for this entire procedure to provide meaningful security benefits, you must authenticate the QMSK out-of-band. Do not skip this step! The standard method is to obtain the QMSK fingerprint from multiple independent sources in several different ways and check to see whether they match the key you just imported. For more information, see How to import and authenticate the Qubes Master Signing Key (https://www.qubes-os.org/security/verifying-signatures/#how-to-import-and-authenticate-the-qubes-master-signing-key).
Tip: After you have authenticated the QMSK out-of-band to your satisfaction, record the QMSK fingerprint in a safe place (or several) so that you don’t have to repeat this step in the future.
Once you are satisfied that you have the genuine QMSK, set its trust level to 5 (“ultimate”), then quit GnuPG with q.
gpg> trust
pub rsa4096/DDFA1A3E36879494
created: 2010-04-01 expires: never usage: SC
trust: unknown validity: unknown
[ unknown] (1). Qubes Master Signing Key
Please decide how far you trust this user to correctly verify other users' keys
(by looking at passports, checking fingerprints from different sources, etc.)
1 = I don't know or won't say
2 = I do NOT trust
3 = I trust marginally
4 = I trust fully
5 = I trust ultimately
m = back to the main menu
Your decision? 5
Do you really want to set this key to ultimate trust? (y/N) y
pub rsa4096/DDFA1A3E36879494
created: 2010-04-01 expires: never usage: SC
trust: ultimate validity: unknown
[ unknown] (1). Qubes Master Signing Key
Please note that the shown key validity is not necessarily correct
unless you restart the program.
gpg> q
Use Git to clone the qubes-secpack repo.
$ git clone https://github.com/QubesOS/qubes-secpack.git
Cloning into 'qubes-secpack'...
remote: Enumerating objects: 4065, done.
remote: Counting objects: 100% (1474/1474), done.
remote: Compressing objects: 100% (742/742), done.
remote: Total 4065 (delta 743), reused 1413 (delta 731), pack-reused 2591
Receiving objects: 100% (4065/4065), 1.64 MiB | 2.53 MiB/s, done.
Resolving deltas: 100% (1910/1910), done.
Import the included PGP keys. (See our PGP key policies (https://www.qubes-os.org/security/pack/#pgp-key-policies) for important information about these keys.)
$ gpg --import qubes-secpack/keys/*/*
gpg: key 063938BA42CFA724: public key "Marek Marczykowski-Górecki (Qubes OS signing key)" imported
gpg: qubes-secpack/keys/core-devs/retired: read error: Is a directory
gpg: no valid OpenPGP data found.
gpg: key 8C05216CE09C093C: 1 signature not checked due to a missing key
gpg: key 8C05216CE09C093C: public key "HW42 (Qubes Signing Key)" imported
gpg: key DA0434BC706E1FCF: public key "Simon Gaiser (Qubes OS signing key)" imported
View the fingerprint of the PGP key you just imported. (Note: gpg> indicates a prompt inside of the GnuPG program. Type what appears after it when prompted.)
$ gpg --edit-key 0x427F11FD0FAA4B080123F01CDDFA1A3E36879494
gpg (GnuPG) 2.2.27; Copyright (C) 2021 Free Software Foundation, Inc.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
pub rsa4096/DDFA1A3E36879494
created: 2010-04-01 expires: never usage: SC
trust: unknown validity: unknown
[ unknown] (1). Qubes Master Signing Key
gpg> fpr
pub rsa4096/DDFA1A3E36879494 2010-04-01 Qubes Master Signing Key
Primary key fingerprint: 427F 11FD 0FAA 4B08 0123 F01C DDFA 1A3E 3687 9494
Important: At this point, you still don’t know whether the key you just imported is the genuine QMSK or a forgery. In order for this entire procedure to provide meaningful security benefits, you must authenticate the QMSK out-of-band. Do not skip this step! The standard method is to obtain the QMSK fingerprint from multiple independent sources in several different ways and check to see whether they match the key you just imported. For more information, see How to import and authenticate the Qubes Master Signing Key (https://www.qubes-os.org/security/verifying-signatures/#how-to-import-and-authenticate-the-qubes-master-signing-key).
Tip: After you have authenticated the QMSK out-of-band to your satisfaction, record the QMSK fingerprint in a safe place (or several) so that you don’t have to repeat this step in the future.
Once you are satisfied that you have the genuine QMSK, set its trust level to 5 (“ultimate”), then quit GnuPG with q.
gpg> trust
pub rsa4096/DDFA1A3E36879494
created: 2010-04-01 expires: never usage: SC
trust: unknown validity: unknown
[ unknown] (1). Qubes Master Signing Key
Please decide how far you trust this user to correctly verify other users' keys
(by looking at passports, checking fingerprints from different sources, etc.)
1 = I don't know or won't say
2 = I do NOT trust
3 = I trust marginally
4 = I trust fully
5 = I trust ultimately
m = back to the main menu
Your decision? 5
Do you really want to set this key to ultimate trust? (y/N) y
pub rsa4096/DDFA1A3E36879494
created: 2010-04-01 expires: never usage: SC
trust: ultimate validity: unknown
[ unknown] (1). Qubes Master Signing Key
Please note that the shown key validity is not necessarily correct
unless you restart the program.
gpg> q
Use Git to clone the qubes-secpack repo.
$ git clone https://github.com/QubesOS/qubes-secpack.git
Cloning into 'qubes-secpack'...
remote: Enumerating objects: 4065, done.
remote: Counting objects: 100% (1474/1474), done.
remote: Compressing objects: 100% (742/742), done.
remote: Total 4065 (delta 743), reused 1413 (delta 731), pack-reused 2591
Receiving objects: 100% (4065/4065), 1.64 MiB | 2.53 MiB/s, done.
Resolving deltas: 100% (1910/1910), done.
Import the included PGP keys. (See our PGP key policies (https://www.qubes-os.org/security/pack/#pgp-key-policies) for important information about these keys.)
$ gpg --import qubes-secpack/keys/*/*
gpg: key 063938BA42CFA724: public key "Marek Marczykowski-Górecki (Qubes OS signing key)" imported
gpg: qubes-secpack/keys/core-devs/retired: read error: Is a directory
gpg: no valid OpenPGP data found.
gpg: key 8C05216CE09C093C: 1 signature not checked due to a missing key
gpg: key 8C05216CE09C093C: public key "HW42 (Qubes Signing Key)" imported
gpg: key DA0434BC706E1FCF: public key "Simon Gaiser (Qubes OS signing key)" imported
gpg: key 8CE137352A019A17: 2 signatures not checked due to missing keys
gpg: key 8CE137352A019A17: public key "Andrew David Wong (Qubes Documentation Signing Key)" imported
gpg: key AAA743B42FBC07A9: public key "Brennan Novak (Qubes Website & Documentation Signing)" imported
gpg: key B6A0BB95CA74A5C3: public key "Joanna Rutkowska (Qubes Documentation Signing Key)" imported
gpg: key F32894BE9684938A: public key "Marek Marczykowski-Górecki (Qubes Documentation Signing Key)" imported
gpg: key 6E7A27B909DAFB92: public key "Hakisho Nukama (Qubes Documentation Signing Key)" imported
gpg: key 485C7504F27D0A72: 1 signature not checked due to a missing key
gpg: key 485C7504F27D0A72: public key "Sven Semmler (Qubes Documentation Signing Key)" imported
gpg: key BB52274595B71262: public key "unman (Qubes Documentation Signing Key)" imported
gpg: key DC2F3678D272F2A8: 1 signature not checked due to a missing key
gpg: key DC2F3678D272F2A8: public key "Wojtek Porczyk (Qubes OS documentation signing key)" imported
gpg: key FD64F4F9E9720C4D: 1 signature not checked due to a missing key
gpg: key FD64F4F9E9720C4D: public key "Zrubi (Qubes Documentation Signing Key)" imported
gpg: key DDFA1A3E36879494: "Qubes Master Signing Key" not changed
gpg: key 1848792F9E2795E9: public key "Qubes OS Release 4 Signing Key" imported
gpg: qubes-secpack/keys/release-keys/retired: read error: Is a directory
gpg: no valid OpenPGP data found.
gpg: key D655A4F21830E06A: public key "Marek Marczykowski-Górecki (Qubes security pack)" imported
gpg: key ACC2602F3F48CB21: public key "Qubes OS Security Team" imported
gpg: qubes-secpack/keys/security-team/retired: read error: Is a directory
gpg: no valid OpenPGP data found.
gpg: key 4AC18DE1112E1490: public key "Simon Gaiser (Qubes Security Pack signing key)" imported
gpg: Total number processed: 17
gpg: imported: 16
gpg: unchanged: 1
gpg: marginals needed: 3 completes needed: 1 trust model: pgp
gpg: depth: 0 valid: 1 signed: 6 trust: 0-, 0q, 0n, 0m, 0f, 1u
gpg: depth: 1 valid: 6 signed: 0 trust: 6-, 0q, 0n, 0m, 0f, 0u
Verify signed Git tags.
$ cd qubes-secpack/
$ git tag -v `git describe`
object 266e14a6fae57c9a91362c9ac784d3a891f4d351
type commit
tag marmarek_sec_266e14a6
tagger Marek Marczykowski-Górecki 1677757924 +0100
Tag for commit 266e14a6fae57c9a91362c9ac784d3a891f4d351
gpg: Signature made Thu 02 Mar 2023 03:52:04 AM PST
gpg: using RSA key 2D1771FE4D767EDC76B089FAD655A4F21830E06A
gpg: Good signature from "Marek Marczykowski-Górecki (Qubes security pack)" [full]
The exact output will differ, but the final line should always start with gpg: Good signature from... followed by an appropriate key. The [full] indicates full trust, which this key inherits in virtue of being validly signed by the QMSK.
Verify PGP signatures, e.g.:
$ cd QSBs/
$ gpg --verify qsb-087-2022.txt.sig.marmarek qsb-087-2022.txt
gpg: Signature made Wed 23 Nov 2022 04:05:51 AM PST
gpg: using RSA key 2D1771FE4D767EDC76B089FAD655A4F21830E06A
gpg: Good signature from "Marek Marczykowski-Górecki (Qubes security pack)" [full]
$ gpg --verify qsb-087-2022.txt.sig.simon qsb-087-2022.txt
gpg: Signature made Wed 23 Nov 2022 03:50:42 AM PST
gpg: using RSA key EA18E7F040C41DDAEFE9AA0F4AC18DE1112E1490
gpg: Good signature from "Simon Gaiser (Qubes Security Pack signing key)" [full]
$ cd ../canaries/
$ gpg --verify canary-034-2023.txt.sig.marmarek canary-034-2023.txt
gpg: Signature made Thu 02 Mar 2023 03:51:48 AM PST
gpg: using RSA key 2D1771FE4D767EDC76B089FAD655A4F21830E06A
gpg: Good signature from "Marek Marczykowski-Górecki (Qubes security pack)" [full]
$ gpg --verify canary-034-2023.txt.sig.simon canary-034-2023.txt
gpg: Signature made Thu 02 Mar 2023 01:47:52 AM PST
gpg: using RSA key EA18E7F040C41DDAEFE9AA0F4AC18DE1112E1490
gpg: key 8CE137352A019A17: public key "Andrew David Wong (Qubes Documentation Signing Key)" imported
gpg: key AAA743B42FBC07A9: public key "Brennan Novak (Qubes Website & Documentation Signing)" imported
gpg: key B6A0BB95CA74A5C3: public key "Joanna Rutkowska (Qubes Documentation Signing Key)" imported
gpg: key F32894BE9684938A: public key "Marek Marczykowski-Górecki (Qubes Documentation Signing Key)" imported
gpg: key 6E7A27B909DAFB92: public key "Hakisho Nukama (Qubes Documentation Signing Key)" imported
gpg: key 485C7504F27D0A72: 1 signature not checked due to a missing key
gpg: key 485C7504F27D0A72: public key "Sven Semmler (Qubes Documentation Signing Key)" imported
gpg: key BB52274595B71262: public key "unman (Qubes Documentation Signing Key)" imported
gpg: key DC2F3678D272F2A8: 1 signature not checked due to a missing key
gpg: key DC2F3678D272F2A8: public key "Wojtek Porczyk (Qubes OS documentation signing key)" imported
gpg: key FD64F4F9E9720C4D: 1 signature not checked due to a missing key
gpg: key FD64F4F9E9720C4D: public key "Zrubi (Qubes Documentation Signing Key)" imported
gpg: key DDFA1A3E36879494: "Qubes Master Signing Key" not changed
gpg: key 1848792F9E2795E9: public key "Qubes OS Release 4 Signing Key" imported
gpg: qubes-secpack/keys/release-keys/retired: read error: Is a directory
gpg: no valid OpenPGP data found.
gpg: key D655A4F21830E06A: public key "Marek Marczykowski-Górecki (Qubes security pack)" imported
gpg: key ACC2602F3F48CB21: public key "Qubes OS Security Team" imported
gpg: qubes-secpack/keys/security-team/retired: read error: Is a directory
gpg: no valid OpenPGP data found.
gpg: key 4AC18DE1112E1490: public key "Simon Gaiser (Qubes Security Pack signing key)" imported
gpg: Total number processed: 17
gpg: imported: 16
gpg: unchanged: 1
gpg: marginals needed: 3 completes needed: 1 trust model: pgp
gpg: depth: 0 valid: 1 signed: 6 trust: 0-, 0q, 0n, 0m, 0f, 1u
gpg: depth: 1 valid: 6 signed: 0 trust: 6-, 0q, 0n, 0m, 0f, 0u
Verify signed Git tags.
$ cd qubes-secpack/
$ git tag -v `git describe`
object 266e14a6fae57c9a91362c9ac784d3a891f4d351
type commit
tag marmarek_sec_266e14a6
tagger Marek Marczykowski-Górecki 1677757924 +0100
Tag for commit 266e14a6fae57c9a91362c9ac784d3a891f4d351
gpg: Signature made Thu 02 Mar 2023 03:52:04 AM PST
gpg: using RSA key 2D1771FE4D767EDC76B089FAD655A4F21830E06A
gpg: Good signature from "Marek Marczykowski-Górecki (Qubes security pack)" [full]
The exact output will differ, but the final line should always start with gpg: Good signature from... followed by an appropriate key. The [full] indicates full trust, which this key inherits in virtue of being validly signed by the QMSK.
Verify PGP signatures, e.g.:
$ cd QSBs/
$ gpg --verify qsb-087-2022.txt.sig.marmarek qsb-087-2022.txt
gpg: Signature made Wed 23 Nov 2022 04:05:51 AM PST
gpg: using RSA key 2D1771FE4D767EDC76B089FAD655A4F21830E06A
gpg: Good signature from "Marek Marczykowski-Górecki (Qubes security pack)" [full]
$ gpg --verify qsb-087-2022.txt.sig.simon qsb-087-2022.txt
gpg: Signature made Wed 23 Nov 2022 03:50:42 AM PST
gpg: using RSA key EA18E7F040C41DDAEFE9AA0F4AC18DE1112E1490
gpg: Good signature from "Simon Gaiser (Qubes Security Pack signing key)" [full]
$ cd ../canaries/
$ gpg --verify canary-034-2023.txt.sig.marmarek canary-034-2023.txt
gpg: Signature made Thu 02 Mar 2023 03:51:48 AM PST
gpg: using RSA key 2D1771FE4D767EDC76B089FAD655A4F21830E06A
gpg: Good signature from "Marek Marczykowski-Górecki (Qubes security pack)" [full]
$ gpg --verify canary-034-2023.txt.sig.simon canary-034-2023.txt
gpg: Signature made Thu 02 Mar 2023 01:47:52 AM PST
gpg: using RSA key EA18E7F040C41DDAEFE9AA0F4AC18DE1112E1490
gpg: Good signature from "Simon Gaiser (Qubes Security Pack signing key)" [full]
Again, the exact output will differ, but the final line of output from each gpg --verify command should always start with gpg: Good signature from... followed by an appropriate key.
For this announcement (QSB-095), the commands are:
$ gpg --verify qsb-095-2023.txt.sig.marmarek qsb-095-2023.txt
$ gpg --verify qsb-095-2023.txt.sig.simon qsb-095-2023.txt
You can also verify the signatures directly from this announcement in addition to or instead of verifying the files from the qubes-secpack. Simply copy and paste the QSB-095 text into a plain text file and do the same for both signature files. Then, perform the same authentication steps as listed above, substituting the filenames above with the names of the files you just created.
Again, the exact output will differ, but the final line of output from each gpg --verify command should always start with gpg: Good signature from... followed by an appropriate key.
For this announcement (QSB-095), the commands are:
$ gpg --verify qsb-095-2023.txt.sig.marmarek qsb-095-2023.txt
$ gpg --verify qsb-095-2023.txt.sig.simon qsb-095-2023.txt
You can also verify the signatures directly from this announcement in addition to or instead of verifying the files from the qubes-secpack. Simply copy and paste the QSB-095 text into a plain text file and do the same for both signature files. Then, perform the same authentication steps as listed above, substituting the filenames above with the names of the files you just created.
👍1
Fedora 37 approaching EOL
https://www.qubes-os.org/news/2023/10/12/fedora-37-approaching-eol/
Fedora 37 is currently scheduled (https://fedorapeople.org/groups/schedule/f-39/f-39-key-tasks.html) to reach EOL (end-of-life (https://fedoraproject.org/wiki/End_of_life)) on 2023-11-21. We strongly recommend that all users upgrade (https://www.qubes-os.org/doc/templates/fedora/#upgrading) their Fedora templates and standalones to Fedora 38 (https://www.qubes-os.org/news/2023/05/26/fedora-38-templates-available/) before then. For more information, see Upgrading to avoid EOL (https://www.qubes-os.org/doc/how-to-update/#upgrading-to-avoid-eol).
There are two ways to upgrade your template to a new Fedora release:
Recommended: Install a fresh template to replace the existing one. (https://www.qubes-os.org/doc/templates/fedora/#installing) This option may be simpler for less experienced users. After you install the new template, redo all desired template modifications and switch everything that was set to the old template to the new template (https://www.qubes-os.org/doc/templates/#switching). You may want to write down the modifications you make to your templates so that you remember what to redo on each fresh install. To see a log of package manager actions, open a terminal in the old Fedora template and use the dnf history command.
Advanced: Perform an in-place upgrade of an existing Fedora template. (https://www.qubes-os.org/doc/templates/fedora/in-place-upgrade/) This option will preserve any modifications you’ve made to the template, but it may be more complicated for less experienced users.
For a complete list of template releases that are supported for your specific Qubes release, see our supported template releases (https://www.qubes-os.org/doc/supported-releases/#templates). Please note that no user action is required regarding the OS version in dom0 (see our note on dom0 and EOL (https://www.qubes-os.org/doc/supported-releases/#note-on-dom0-and-eol)).
https://www.qubes-os.org/news/2023/10/12/fedora-37-approaching-eol/
Fedora 37 is currently scheduled (https://fedorapeople.org/groups/schedule/f-39/f-39-key-tasks.html) to reach EOL (end-of-life (https://fedoraproject.org/wiki/End_of_life)) on 2023-11-21. We strongly recommend that all users upgrade (https://www.qubes-os.org/doc/templates/fedora/#upgrading) their Fedora templates and standalones to Fedora 38 (https://www.qubes-os.org/news/2023/05/26/fedora-38-templates-available/) before then. For more information, see Upgrading to avoid EOL (https://www.qubes-os.org/doc/how-to-update/#upgrading-to-avoid-eol).
There are two ways to upgrade your template to a new Fedora release:
Recommended: Install a fresh template to replace the existing one. (https://www.qubes-os.org/doc/templates/fedora/#installing) This option may be simpler for less experienced users. After you install the new template, redo all desired template modifications and switch everything that was set to the old template to the new template (https://www.qubes-os.org/doc/templates/#switching). You may want to write down the modifications you make to your templates so that you remember what to redo on each fresh install. To see a log of package manager actions, open a terminal in the old Fedora template and use the dnf history command.
Advanced: Perform an in-place upgrade of an existing Fedora template. (https://www.qubes-os.org/doc/templates/fedora/in-place-upgrade/) This option will preserve any modifications you’ve made to the template, but it may be more complicated for less experienced users.
For a complete list of template releases that are supported for your specific Qubes release, see our supported template releases (https://www.qubes-os.org/doc/supported-releases/#templates). Please note that no user action is required regarding the OS version in dom0 (see our note on dom0 and EOL (https://www.qubes-os.org/doc/supported-releases/#note-on-dom0-and-eol)).
❤4
Qubes OS 4.2.0-rc4 is available for testing
https://www.qubes-os.org/news/2023/10/13/qubes-os-4-2-0-rc4-available-for-testing/
We’re pleased to announce that the fourth release candidate (RC) (https://www.qubes-os.org/news/2023/10/13/qubes-os-4-2-0-rc4-available-for-testing/#what-is-a-release-candidate) for Qubes OS 4.2.0 is now available for testing (https://www.qubes-os.org/doc/testing/). The ISO and associated verification files (https://www.qubes-os.org/security/verifying-signatures/) are available on the downloads (https://www.qubes-os.org/downloads/) page.
Main changes from RC3 to RC4
Fixed: “qvm-move fails, deletes origin file anyway” (#8516) (https://github.com/QubesOS/qubes-issues/issues/8516)
Fixed: “90-default.policy not upgraded after in-place upgrade from 4.1 to 4.2” (#8458)
Fixed: “Qube Manager freezes while opening settings” (#8387) (https://github.com/QubesOS/qubes-issues/issues/8387)
Fixed: “Error when attempting to update dom0 in the Qube Manager” (#8117) (https://github.com/QubesOS/qubes-issues/issues/8117)
Fixed: “XScreenSaver & XScreenSaver Settings not opening window” (#8266) (https://github.com/QubesOS/qubes-issues/issues/8266)
Fixed: “Setting no-strict-reset option via salt on already attached devices doesn’t work” (#8514) (https://github.com/QubesOS/qubes-issues/issues/8514)
Fixed: “qvm-copy-to-vm incorrect progress report” (#1519) (https://github.com/QubesOS/qubes-issues/issues/1519)
Fixed: “qubes-video-companion-receiver missing dependency on acl package” (#8426) (https://github.com/QubesOS/qubes-issues/issues/8426)
Fixed: “OpenBSD 7.3 ISO doesn’t boot anymore” (#8502) (https://github.com/QubesOS/qubes-issues/issues/8502)
Fixed: “Kernel compile bogs down rest of system” (#8176) (https://github.com/QubesOS/qubes-issues/issues/8176)
Fixed: “rpm-oxide makes unjustified assumptions about RPM ABI” (#8522) (https://github.com/QubesOS/qubes-issues/issues/8522)
Fixed: “yk-auth YubiKey PAM noscript incorrectly expects \0 to be appended to hash” (#8517) (https://github.com/QubesOS/qubes-issues/issues/8517)
Fixed: “Qubes Application Menu isn’t updated when using salt to modify menu-items” (#8494) (https://github.com/QubesOS/qubes-issues/issues/8494)
Fixed: “Different values for menu-items and default-menu-items are not preserved when cloning templates” (#8518)
Fixed: “Fix handling of menu items in GUI VM” (#8528) (https://github.com/QubesOS/qubes-issues/issues/8528)
Fixed: “Firefox does not start on 4.2-rc3 after upgrading template” (#8571) (https://github.com/QubesOS/qubes-issues/issues/8571)
Fixed: “Qubes R4.2.0-rc2 Qubes OS Global Config tool not see qubes-u2f installed in sys-usb” (#8463) (https://github.com/QubesOS/qubes-issues/issues/8463)
Fixed: “global config: policy rules for U2F incorrectly assume wildcard argument” (#8525) (https://github.com/QubesOS/qubes-issues/issues/8525)
Fixed: “Pipewire on some systems causes a lot of underruns” (#8576) (https://github.com/QubesOS/qubes-issues/issues/8576)
Fixed: “Listing PCI devices breaks when there is some with non-0000 PCI domain” (#6932) (https://github.com/QubesOS/qubes-issues/issues/6932)
Done: “Prepare R4.1 -> R4.2 upgrade tool” (#7832) (https://github.com/QubesOS/qubes-issues/issues/7832)
Done: “Phase out legacy qrexec policy files” (#8000) (https://github.com/QubesOS/qubes-issues/issues/8000)
Done: “Better qrexec service configuration format” (#8153) (https://github.com/QubesOS/qubes-issues/issues/8153)
Done: “QRexec services should be able to specify the user they must run as” (#6354) (https://github.com/QubesOS/qubes-issues/issues/6354)
Done: “Qube Manager: Enable the ‘restart qube’ button for named disposables” (#8382) (https://github.com/QubesOS/qubes-issues/issues/8382)
Done: “Utilize memory hotplug to add VM memory by qmemman” (#7956) (https://github.com/QubesOS/qubes-issues/issues/7956)
https://www.qubes-os.org/news/2023/10/13/qubes-os-4-2-0-rc4-available-for-testing/
We’re pleased to announce that the fourth release candidate (RC) (https://www.qubes-os.org/news/2023/10/13/qubes-os-4-2-0-rc4-available-for-testing/#what-is-a-release-candidate) for Qubes OS 4.2.0 is now available for testing (https://www.qubes-os.org/doc/testing/). The ISO and associated verification files (https://www.qubes-os.org/security/verifying-signatures/) are available on the downloads (https://www.qubes-os.org/downloads/) page.
Main changes from RC3 to RC4
Fixed: “qvm-move fails, deletes origin file anyway” (#8516) (https://github.com/QubesOS/qubes-issues/issues/8516)
Fixed: “90-default.policy not upgraded after in-place upgrade from 4.1 to 4.2” (#8458)
Fixed: “Qube Manager freezes while opening settings” (#8387) (https://github.com/QubesOS/qubes-issues/issues/8387)
Fixed: “Error when attempting to update dom0 in the Qube Manager” (#8117) (https://github.com/QubesOS/qubes-issues/issues/8117)
Fixed: “XScreenSaver & XScreenSaver Settings not opening window” (#8266) (https://github.com/QubesOS/qubes-issues/issues/8266)
Fixed: “Setting no-strict-reset option via salt on already attached devices doesn’t work” (#8514) (https://github.com/QubesOS/qubes-issues/issues/8514)
Fixed: “qvm-copy-to-vm incorrect progress report” (#1519) (https://github.com/QubesOS/qubes-issues/issues/1519)
Fixed: “qubes-video-companion-receiver missing dependency on acl package” (#8426) (https://github.com/QubesOS/qubes-issues/issues/8426)
Fixed: “OpenBSD 7.3 ISO doesn’t boot anymore” (#8502) (https://github.com/QubesOS/qubes-issues/issues/8502)
Fixed: “Kernel compile bogs down rest of system” (#8176) (https://github.com/QubesOS/qubes-issues/issues/8176)
Fixed: “rpm-oxide makes unjustified assumptions about RPM ABI” (#8522) (https://github.com/QubesOS/qubes-issues/issues/8522)
Fixed: “yk-auth YubiKey PAM noscript incorrectly expects \0 to be appended to hash” (#8517) (https://github.com/QubesOS/qubes-issues/issues/8517)
Fixed: “Qubes Application Menu isn’t updated when using salt to modify menu-items” (#8494) (https://github.com/QubesOS/qubes-issues/issues/8494)
Fixed: “Different values for menu-items and default-menu-items are not preserved when cloning templates” (#8518)
Fixed: “Fix handling of menu items in GUI VM” (#8528) (https://github.com/QubesOS/qubes-issues/issues/8528)
Fixed: “Firefox does not start on 4.2-rc3 after upgrading template” (#8571) (https://github.com/QubesOS/qubes-issues/issues/8571)
Fixed: “Qubes R4.2.0-rc2 Qubes OS Global Config tool not see qubes-u2f installed in sys-usb” (#8463) (https://github.com/QubesOS/qubes-issues/issues/8463)
Fixed: “global config: policy rules for U2F incorrectly assume wildcard argument” (#8525) (https://github.com/QubesOS/qubes-issues/issues/8525)
Fixed: “Pipewire on some systems causes a lot of underruns” (#8576) (https://github.com/QubesOS/qubes-issues/issues/8576)
Fixed: “Listing PCI devices breaks when there is some with non-0000 PCI domain” (#6932) (https://github.com/QubesOS/qubes-issues/issues/6932)
Done: “Prepare R4.1 -> R4.2 upgrade tool” (#7832) (https://github.com/QubesOS/qubes-issues/issues/7832)
Done: “Phase out legacy qrexec policy files” (#8000) (https://github.com/QubesOS/qubes-issues/issues/8000)
Done: “Better qrexec service configuration format” (#8153) (https://github.com/QubesOS/qubes-issues/issues/8153)
Done: “QRexec services should be able to specify the user they must run as” (#6354) (https://github.com/QubesOS/qubes-issues/issues/6354)
Done: “Qube Manager: Enable the ‘restart qube’ button for named disposables” (#8382) (https://github.com/QubesOS/qubes-issues/issues/8382)
Done: “Utilize memory hotplug to add VM memory by qmemman” (#7956) (https://github.com/QubesOS/qubes-issues/issues/7956)
For an overview of major changes from Qubes 4.1 to 4.2, please see the Qubes OS 4.2.0 release notes (https://www.qubes-os.org/doc/releases/4.2/release-notes/).
When is the stable release?
That depends on the number of bugs discovered in this RC and their severity. As explained in our release schedule (https://www.qubes-os.org/doc/version-scheme/#release-schedule) documentation, our usual process after issuing a new RC is to collect bug reports, triage the bugs, and fix them. This usually takes around five weeks, depending on the bugs discovered. If warranted, we then issue a new RC that includes the fixes and repeat the whole process again. We continue this iterative procedure until we’re left with an RC that’s good enough to be declared the stable release. No one can predict, at the outset, how many iterations will be required (and hence how many RCs will be needed before a stable release), but we tend to get a clearer picture of this with each successive RC, which we share in this section in each RC announcement. Here is the latest update:
At this point, we are hopeful that RC4 will be the final RC.
Testing Qubes 4.2.0-rc4
Thank you to everyone who tested the previous Qubes 4.2.0 RCs! Due to your efforts, this new RC includes fixes for several bugs that were present in the previous RCs.
If you’re willing to test (https://www.qubes-os.org/doc/testing/) this new RC, you can help us improve the eventual stable release by reporting any bugs you encounter (https://www.qubes-os.org/doc/issue-tracking/). We encourage experienced users to join the testing team (https://forum.qubes-os.org/t/joining-the-testing-team/5190).
A full list of issues affecting Qubes 4.2.0 is available here (https://github.com/QubesOS/qubes-issues/issues?q=is%3Aissue+label%3Aaffects-4.2). We strongly recommend updating Qubes OS (https://www.qubes-os.org/doc/how-to-update/) immediately after installation in order to apply all available bug fixes.
Upgrading to Qubes 4.2.0-rc4
If you’re currently running any Qubes 4.2.0 RC, you can upgrade to the latest RC by enabling the current-testing repo in dom0, then updating normally (https://www.qubes-os.org/doc/how-to-update/). However, please note that there have been some recent template changes, which are detailed in the Qubes OS 4.2.0 release notes (https://www.qubes-os.org/doc/releases/4.2/release-notes/).
If you’re currently on Qubes 4.1 and wish to test 4.2, please see how to upgrade to Qubes 4.2 (https://www.qubes-os.org/doc/upgrade/4.2/), which details both clean installation and in-place upgrade options. As always, we strongly recommend making a full backup (https://www.qubes-os.org/doc/how-to-back-up-restore-and-migrate/) beforehand.
Reminder: new signing key for Qubes OS 4.2
As a reminder, we published the following special announcement in Qubes Canary 032 (https://www.qubes-os.org/news/2022/09/14/canary-032/) on 2022-09-14:
We plan to create a new Release Signing Key (RSK) for Qubes OS 4.2. Normally, we have only one RSK for each major release. However, for the 4.2 release, we will be using Qubes Builder version 2, which is a complete rewrite of the Qubes Builder. Out of an abundance of caution, we would like to isolate the build processes of the current stable 4.1 release and the upcoming 4.2 release from each other at the cryptographic level in order to minimize the risk of a vulnerability in one affecting the other. We are including this notice as a canary special announcement since introducing a new RSK for a minor release is an exception to our usual RSK management policy.
As always, we encourage you to authenticate (https://www.qubes-os.org/security/pack/#how-to-obtain-and-authenticate) this canary by verifying its PGP signatures (https://www.qubes-os.org/security/verifying-signatures/). Specific instructions are also included in the canary announcement (https://www.qubes-os.org/news/2022/09/14/canary-032/).
When is the stable release?
That depends on the number of bugs discovered in this RC and their severity. As explained in our release schedule (https://www.qubes-os.org/doc/version-scheme/#release-schedule) documentation, our usual process after issuing a new RC is to collect bug reports, triage the bugs, and fix them. This usually takes around five weeks, depending on the bugs discovered. If warranted, we then issue a new RC that includes the fixes and repeat the whole process again. We continue this iterative procedure until we’re left with an RC that’s good enough to be declared the stable release. No one can predict, at the outset, how many iterations will be required (and hence how many RCs will be needed before a stable release), but we tend to get a clearer picture of this with each successive RC, which we share in this section in each RC announcement. Here is the latest update:
At this point, we are hopeful that RC4 will be the final RC.
Testing Qubes 4.2.0-rc4
Thank you to everyone who tested the previous Qubes 4.2.0 RCs! Due to your efforts, this new RC includes fixes for several bugs that were present in the previous RCs.
If you’re willing to test (https://www.qubes-os.org/doc/testing/) this new RC, you can help us improve the eventual stable release by reporting any bugs you encounter (https://www.qubes-os.org/doc/issue-tracking/). We encourage experienced users to join the testing team (https://forum.qubes-os.org/t/joining-the-testing-team/5190).
A full list of issues affecting Qubes 4.2.0 is available here (https://github.com/QubesOS/qubes-issues/issues?q=is%3Aissue+label%3Aaffects-4.2). We strongly recommend updating Qubes OS (https://www.qubes-os.org/doc/how-to-update/) immediately after installation in order to apply all available bug fixes.
Upgrading to Qubes 4.2.0-rc4
If you’re currently running any Qubes 4.2.0 RC, you can upgrade to the latest RC by enabling the current-testing repo in dom0, then updating normally (https://www.qubes-os.org/doc/how-to-update/). However, please note that there have been some recent template changes, which are detailed in the Qubes OS 4.2.0 release notes (https://www.qubes-os.org/doc/releases/4.2/release-notes/).
If you’re currently on Qubes 4.1 and wish to test 4.2, please see how to upgrade to Qubes 4.2 (https://www.qubes-os.org/doc/upgrade/4.2/), which details both clean installation and in-place upgrade options. As always, we strongly recommend making a full backup (https://www.qubes-os.org/doc/how-to-back-up-restore-and-migrate/) beforehand.
Reminder: new signing key for Qubes OS 4.2
As a reminder, we published the following special announcement in Qubes Canary 032 (https://www.qubes-os.org/news/2022/09/14/canary-032/) on 2022-09-14:
We plan to create a new Release Signing Key (RSK) for Qubes OS 4.2. Normally, we have only one RSK for each major release. However, for the 4.2 release, we will be using Qubes Builder version 2, which is a complete rewrite of the Qubes Builder. Out of an abundance of caution, we would like to isolate the build processes of the current stable 4.1 release and the upcoming 4.2 release from each other at the cryptographic level in order to minimize the risk of a vulnerability in one affecting the other. We are including this notice as a canary special announcement since introducing a new RSK for a minor release is an exception to our usual RSK management policy.
As always, we encourage you to authenticate (https://www.qubes-os.org/security/pack/#how-to-obtain-and-authenticate) this canary by verifying its PGP signatures (https://www.qubes-os.org/security/verifying-signatures/). Specific instructions are also included in the canary announcement (https://www.qubes-os.org/news/2022/09/14/canary-032/).
❤2
As with all Qubes signing keys, we also encourage you to authenticate (https://www.qubes-os.org/security/verifying-signatures/#how-to-import-and-authenticate-release-signing-keys) the new Qubes OS Release 4.2 Signing Key, which is available in the Qubes Security Pack (qubes-secpack) (https://www.qubes-os.org/security/pack/) as well as on the downloads (https://www.qubes-os.org/downloads/) page under the Qubes OS 4.2.0-rc4 ISO.
What is a release candidate?
A release candidate (RC) is a software build that has the potential to become a stable release, unless significant bugs are discovered in testing. RCs are intended for more advanced (or adventurous!) users who are comfortable testing early versions of software that are potentially buggier than stable releases. You can read more about Qubes OS supported releases (https://www.qubes-os.org/doc/supported-releases/) and the version scheme (https://www.qubes-os.org/doc/version-scheme/) in our documentation.
What is a release candidate?
A release candidate (RC) is a software build that has the potential to become a stable release, unless significant bugs are discovered in testing. RCs are intended for more advanced (or adventurous!) users who are comfortable testing early versions of software that are potentially buggier than stable releases. You can read more about Qubes OS supported releases (https://www.qubes-os.org/doc/supported-releases/) and the version scheme (https://www.qubes-os.org/doc/version-scheme/) in our documentation.
👍1
XSAs released on 2023-11-14
https://www.qubes-os.org/news/2023/11/14/xsas-released-on-2023-11-14/
The Xen Project (https://xenproject.org/) has released one or more Xen security advisories (XSAs) (https://xenbits.xen.org/xsa/).
The security of Qubes OS is affected by at least one of these XSAs.
XSAs that DO affect the security of Qubes OS
The following XSAs do affect the security of Qubes OS:
XSA-446 (https://xenbits.xen.org/xsa/advisory-446.html)
For more information, see QSB-096 (https://www.qubes-os.org/news/2023/11/14/qsb-096/).
XSAs that DO NOT affect the security of Qubes OS
The following XSAs do not affect the security of Qubes OS, and no user action is necessary:
XSA-445 (https://xenbits.xen.org/xsa/advisory-445.html)
Qubes OS uses only “basic” quarantine mode.
About this announcement
Qubes OS uses the Xen hypervisor (https://wiki.xenproject.org/wiki/Xen_Project_Software_Overview) as part of its architecture (https://www.qubes-os.org/doc/architecture/). When the Xen Project (https://xenproject.org/) publicly discloses a vulnerability in the Xen hypervisor, they issue a notice called a Xen security advisory (XSA) (https://xenproject.org/developers/security-policy/). Vulnerabilities in the Xen hypervisor sometimes have security implications for Qubes OS. When they do, we issue a notice called a Qubes security bulletin (QSB) (https://www.qubes-os.org/security/qsb/). (QSBs are also issued for non-Xen vulnerabilities.) However, QSBs can provide only positive confirmation that certain XSAs do affect the security of Qubes OS. QSBs cannot provide negative confirmation that other XSAs do not affect the security of Qubes OS. Therefore, we also maintain an XSA tracker (https://www.qubes-os.org/security/xsa/), which is a comprehensive list of all XSAs publicly disclosed to date, including whether each one affects the security of Qubes OS. When new XSAs are published, we add them to the XSA tracker and publish a notice like this one in order to inform Qubes users that a new batch of XSAs has been released and whether each one affects the security of Qubes OS.
https://www.qubes-os.org/news/2023/11/14/xsas-released-on-2023-11-14/
The Xen Project (https://xenproject.org/) has released one or more Xen security advisories (XSAs) (https://xenbits.xen.org/xsa/).
The security of Qubes OS is affected by at least one of these XSAs.
XSAs that DO affect the security of Qubes OS
The following XSAs do affect the security of Qubes OS:
XSA-446 (https://xenbits.xen.org/xsa/advisory-446.html)
For more information, see QSB-096 (https://www.qubes-os.org/news/2023/11/14/qsb-096/).
XSAs that DO NOT affect the security of Qubes OS
The following XSAs do not affect the security of Qubes OS, and no user action is necessary:
XSA-445 (https://xenbits.xen.org/xsa/advisory-445.html)
Qubes OS uses only “basic” quarantine mode.
About this announcement
Qubes OS uses the Xen hypervisor (https://wiki.xenproject.org/wiki/Xen_Project_Software_Overview) as part of its architecture (https://www.qubes-os.org/doc/architecture/). When the Xen Project (https://xenproject.org/) publicly discloses a vulnerability in the Xen hypervisor, they issue a notice called a Xen security advisory (XSA) (https://xenproject.org/developers/security-policy/). Vulnerabilities in the Xen hypervisor sometimes have security implications for Qubes OS. When they do, we issue a notice called a Qubes security bulletin (QSB) (https://www.qubes-os.org/security/qsb/). (QSBs are also issued for non-Xen vulnerabilities.) However, QSBs can provide only positive confirmation that certain XSAs do affect the security of Qubes OS. QSBs cannot provide negative confirmation that other XSAs do not affect the security of Qubes OS. Therefore, we also maintain an XSA tracker (https://www.qubes-os.org/security/xsa/), which is a comprehensive list of all XSAs publicly disclosed to date, including whether each one affects the security of Qubes OS. When new XSAs are published, we add them to the XSA tracker and publish a notice like this one in order to inform Qubes users that a new batch of XSAs has been released and whether each one affects the security of Qubes OS.
QSB-096: BTC/SRSO fixes not fully effective (XSA-446)
https://www.qubes-os.org/news/2023/11/14/qsb-096/
We have published Qubes Security Bulletin 096: BTC/SRSO fixes not fully effective (XSA-446) (https://github.com/QubesOS/qubes-secpack/blob/main/QSBs/qsb-096-2023.txt). The text of this QSB and its accompanying cryptographic signatures are reproduced below. For an explanation of this announcement and instructions for authenticating this QSB, please see the end of this announcement.
Qubes Security Bulletin 096
---===[ Qubes Security Bulletin 096 ]===---
2023-11-14
BTC/SRSO fixes not fully effective (XSA-446)
User action
------------
Continue to update normally [1] in order to receive the security updates
described in the "Patching" section below. No other user action is
required in response to this QSB.
Summary
--------
On 2023-11-14, the Xen Project published XSA-446, "x86: BTC/SRSO fixes
not fully effective" [3]:
| The fixes for XSA-422 (Branch Type Confusion) and XSA-434 (Speculative
| Return Stack Overflow) are not IRQ-safe. It was believed that the
| mitigations always operated in contexts with IRQs disabled.
|
| However, the original XSA-254 fix for Meltdown (XPTI) deliberately
| left interrupts enabled on two entry paths; one unconditionally, and
| one conditionally on whether XPTI was active.
|
| As BTC/SRSO and Meltdown affect different CPU vendors, the mitigations
| are not active together by default. Therefore, there is race
| condition whereby a malicious PV guest can bypass BTC/SRSO protections
| and launch a BTC/SRSO attack against Xen.
Impact
-------
The impact is the same as it was in QSB-086 [4]:
| On Qubes OS installations with affected CPUs, a VM running in PV mode
| may be capable of inferring the memory contents of other running VMs,
| including dom0. In the default Qubes OS configuration, only the
| stubdomains for HVMs are in a position to exploit this vulnerability
| in order to attack other VMs. (Dom0 also runs in PV mode, but it is
| fully trusted.)
Affected systems
-----------------
Only x86 AMD and Hygon systems are vulnerable.
Patching
---------
The following packages contain security updates that address the
vulnerabilities described in this bulletin:
For Qubes 4.1, in dom0:
- Xen packages, version 4.14.6-4
For Qubes 4.2, in dom0:
- Xen packages, version 4.17.2-5
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. [2] Once available, the packages are to be installed
via the Qubes Update tool or its command-line equivalents. [1]
Dom0 must be restarted afterward in order for the updates to take
effect.
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://www.qubes-os.org/doc/how-to-update/
[2] https://www.qubes-os.org/doc/testing/
[3] https://xenbits.xen.org/xsa/advisory-446.html
[4] https://www.qubes-os.org/news/2022/11/08/qsb-086/
--
The Qubes Security Team
https://www.qubes-os.org/security/
Source: https://github.com/QubesOS/qubes-secpack/blob/main/QSBs/qsb-096-2023.txt
Marek Marczykowski-Górecki (https://www.qubes-os.org/team/#marek-marczykowski-g%C3%B3recki)’s PGP signature
-----BEGIN PGP SIGNATURE-----
iQIzBAABCAAdFiEELRdx/k12ftx2sIn61lWk8hgw4GoFAmVTb1UACgkQ1lWk8hgw
4Gq4Ww//UOcTUI/oCJx62nakaxcXZDhYsTBpuQasjp2WFuo7Yz3mYXgAp8EkSvMZ
IdMfeMsbcF2D/UNZ7XxZ+F7yUVeffyqDpTPuBoFehlHokI8Vt0MOLEbipxd4DaoI
LB2lFR9o3OYw0TQvUEmqJH/qkvTZMzeGe7l+OAVcwkjSwNzCvObj3wtR50QbMjWk
Fd11X7YfPRjkeDNCYJ3sFMg30AgGUnp/Ed+CkMFMpfGNPZk2bzNyjY16ALscgVwq
61/rfdP+WgrAy4JqdQXngk1i1s7EKRhzibB7/jqlhQ4Vn6FCtTvd260hTjHNaVRd
75OxTaQGkFCtBxToLK3c56umk10Iyn7ckffSDhFcEaJviXsjO7CnGVrlnJDvHazx
https://www.qubes-os.org/news/2023/11/14/qsb-096/
We have published Qubes Security Bulletin 096: BTC/SRSO fixes not fully effective (XSA-446) (https://github.com/QubesOS/qubes-secpack/blob/main/QSBs/qsb-096-2023.txt). The text of this QSB and its accompanying cryptographic signatures are reproduced below. For an explanation of this announcement and instructions for authenticating this QSB, please see the end of this announcement.
Qubes Security Bulletin 096
---===[ Qubes Security Bulletin 096 ]===---
2023-11-14
BTC/SRSO fixes not fully effective (XSA-446)
User action
------------
Continue to update normally [1] in order to receive the security updates
described in the "Patching" section below. No other user action is
required in response to this QSB.
Summary
--------
On 2023-11-14, the Xen Project published XSA-446, "x86: BTC/SRSO fixes
not fully effective" [3]:
| The fixes for XSA-422 (Branch Type Confusion) and XSA-434 (Speculative
| Return Stack Overflow) are not IRQ-safe. It was believed that the
| mitigations always operated in contexts with IRQs disabled.
|
| However, the original XSA-254 fix for Meltdown (XPTI) deliberately
| left interrupts enabled on two entry paths; one unconditionally, and
| one conditionally on whether XPTI was active.
|
| As BTC/SRSO and Meltdown affect different CPU vendors, the mitigations
| are not active together by default. Therefore, there is race
| condition whereby a malicious PV guest can bypass BTC/SRSO protections
| and launch a BTC/SRSO attack against Xen.
Impact
-------
The impact is the same as it was in QSB-086 [4]:
| On Qubes OS installations with affected CPUs, a VM running in PV mode
| may be capable of inferring the memory contents of other running VMs,
| including dom0. In the default Qubes OS configuration, only the
| stubdomains for HVMs are in a position to exploit this vulnerability
| in order to attack other VMs. (Dom0 also runs in PV mode, but it is
| fully trusted.)
Affected systems
-----------------
Only x86 AMD and Hygon systems are vulnerable.
Patching
---------
The following packages contain security updates that address the
vulnerabilities described in this bulletin:
For Qubes 4.1, in dom0:
- Xen packages, version 4.14.6-4
For Qubes 4.2, in dom0:
- Xen packages, version 4.17.2-5
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. [2] Once available, the packages are to be installed
via the Qubes Update tool or its command-line equivalents. [1]
Dom0 must be restarted afterward in order for the updates to take
effect.
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://www.qubes-os.org/doc/how-to-update/
[2] https://www.qubes-os.org/doc/testing/
[3] https://xenbits.xen.org/xsa/advisory-446.html
[4] https://www.qubes-os.org/news/2022/11/08/qsb-086/
--
The Qubes Security Team
https://www.qubes-os.org/security/
Source: https://github.com/QubesOS/qubes-secpack/blob/main/QSBs/qsb-096-2023.txt
Marek Marczykowski-Górecki (https://www.qubes-os.org/team/#marek-marczykowski-g%C3%B3recki)’s PGP signature
-----BEGIN PGP SIGNATURE-----
iQIzBAABCAAdFiEELRdx/k12ftx2sIn61lWk8hgw4GoFAmVTb1UACgkQ1lWk8hgw
4Gq4Ww//UOcTUI/oCJx62nakaxcXZDhYsTBpuQasjp2WFuo7Yz3mYXgAp8EkSvMZ
IdMfeMsbcF2D/UNZ7XxZ+F7yUVeffyqDpTPuBoFehlHokI8Vt0MOLEbipxd4DaoI
LB2lFR9o3OYw0TQvUEmqJH/qkvTZMzeGe7l+OAVcwkjSwNzCvObj3wtR50QbMjWk
Fd11X7YfPRjkeDNCYJ3sFMg30AgGUnp/Ed+CkMFMpfGNPZk2bzNyjY16ALscgVwq
61/rfdP+WgrAy4JqdQXngk1i1s7EKRhzibB7/jqlhQ4Vn6FCtTvd260hTjHNaVRd
75OxTaQGkFCtBxToLK3c56umk10Iyn7ckffSDhFcEaJviXsjO7CnGVrlnJDvHazx
Vs1S5G+3hiLo205XSozrmR8bmNopEuOVa4zAshCh6v/Gl4Zmn8Za5dkS6xEBr0jL
TWEi8/G9ZD5g3Iz+4GL9T4n9aTCAC92hcp7qVNytRO5RD8HE3B2JDOQvJ5bNpZQB
a2H5tIWlilgfY2HVndfezafF4D6CV3F5SZ9ZpRlLGw6soYfIFSaj2pmhTlqPHjPA
8Z6RoQ4PJ+ErWL7vRjmyz1Jp5x2lhUxis94+p1of4NkipK6/jVRMXxIe4bQ2r96o
aWcShpnLI3wW5WeMwQf5uNAmYmwxmqhZYQA6LK4EJg6NN5P2Xz8=
=nzwT
-----END PGP SIGNATURE-----
Source: https://github.com/QubesOS/qubes-secpack/blob/main/QSBs/qsb-096-2023.txt.sig.marmarek
Simon Gaiser (aka HW42) (https://www.qubes-os.org/team/#simon-gaiser-aka-hw42)’s PGP signature
-----BEGIN PGP SIGNATURE-----
iQIzBAABCgAdFiEE6hjn8EDEHdrv6aoPSsGN4REuFJAFAmVTNYAACgkQSsGN4REu
FJBLqw/8Cq16ZBx7TJnlF4c1NnqJ3EBUf9VNl8/poZEvUKTVV/68UjJa8uEvD7n+
PHgNko7yrNXIRPAS7zLs4w0gtd8vN7COQetARS8QX2YSLoNb+564ElNm8VXxOdKx
eA6xzNUww6javbyoSCPqwMGia2FkAjcjxY5L4CFCjXx+5uS+Qom9+MaTVskroHAZ
dXE37TILGDsTTBQZnX/phPxUZTQK7gIbKwFlrOSmj0QVslHF2/dRNpM3wmEQqhzj
g/vOuA+TO86mW+rrYOHCIJFarAkrOtJQ7RDDNUP2P9hgOxg8qiCchdEMJPiC+uMW
xpZ+XSzjlJSXVlSdg/4Q0ZQ2SxK1he+mTkRBxgjxYfam1JAiTWLDVMxWjH7zvyeH
Ymk92gIfJRcTrdELCY7K6KCBk+y7dIfm47UmyeSmGtRSuhqFvJUvE9GZl2BPUd7f
cejkJCegJ6lxAWxQmzQ0lOq9j0PaqqbxOcIyq+DBaMfDWExKeOvmzajHFKWPUBqs
TpYGSqvVzhkstgqid5t0vR8WbH1GpHRSUo6ytEREkIJ6KShFGeknju60EiRNDEcA
SvFIp01pjzO/q3px3ywNheZ7zNP/B3wr/P2e7U1mxg0sBy4QMQxqsUtscsJZMpZe
hl1XBjqYLpeppAq9kohZUV1H++q1WMxUJ72PXEiX2DRT8RxLl5w=
=ANw6
-----END PGP SIGNATURE-----
Source: https://github.com/QubesOS/qubes-secpack/blob/main/QSBs/qsb-096-2023.txt.sig.simon
What is the purpose of this announcement?
The purpose of this announcement is to inform the Qubes community that a new Qubes security bulletin (QSB) has been published.
What is a Qubes security bulletin (QSB)?
A Qubes security bulletin (QSB) is a security announcement issued by the Qubes security team (https://www.qubes-os.org/security/#qubes-security-team). A QSB typically provides a summary and impact analysis of one or more recently-discovered software vulnerabilities, including details about patching to address them. For a list of all QSBs, see Qubes security bulletins (QSBs) (https://www.qubes-os.org/security/qsb/).
Why should I care about QSBs?
QSBs tell you what actions you must take in order to protect yourself from recently-discovered security vulnerabilities. In most cases, security vulnerabilities are addressed by updating normally (https://www.qubes-os.org/doc/how-to-update/). However, in some cases, special user action is required. In all cases, the required actions are detailed in QSBs.
What are the PGP signatures that accompany QSBs?
A PGP (https://en.wikipedia.org/wiki/Pretty_Good_Privacy) signature is a cryptographic digital signature (https://en.wikipedia.org/wiki/Digital_signature) made in accordance with the OpenPGP (https://en.wikipedia.org/wiki/Pretty_Good_Privacy#OpenPGP) standard. PGP signatures can be cryptographically verified with programs like GNU Privacy Guard (GPG) (https://gnupg.org/). The Qubes security team cryptographically signs all QSBs so that Qubes users have a reliable way to check whether QSBs are genuine. The only way to be certain that a QSB is authentic is by verifying its PGP signatures.
Why should I care whether a QSB is authentic?
A forged QSB could deceive you into taking actions that adversely affect the security of your Qubes OS system, such as installing malware or making configuration changes that render your system vulnerable to attack. Falsified QSBs could sow fear, uncertainty, and doubt about the security of Qubes OS or the status of the Qubes OS Project.
How do I verify the PGP signatures on a QSB?
The following command-line instructions assume a Linux system with git and gpg installed. (For Windows and Mac options, see OpenPGP software (https://www.qubes-os.org/security/verifying-signatures/#openpgp-software).)
Obtain the Qubes Master Signing Key (QMSK), e.g.:
$ gpg --fetch-keys https://keys.qubes-os.org/keys/qubes-master-signing-key.asc
gpg: directory '/home/user/.gnupg' created
TWEi8/G9ZD5g3Iz+4GL9T4n9aTCAC92hcp7qVNytRO5RD8HE3B2JDOQvJ5bNpZQB
a2H5tIWlilgfY2HVndfezafF4D6CV3F5SZ9ZpRlLGw6soYfIFSaj2pmhTlqPHjPA
8Z6RoQ4PJ+ErWL7vRjmyz1Jp5x2lhUxis94+p1of4NkipK6/jVRMXxIe4bQ2r96o
aWcShpnLI3wW5WeMwQf5uNAmYmwxmqhZYQA6LK4EJg6NN5P2Xz8=
=nzwT
-----END PGP SIGNATURE-----
Source: https://github.com/QubesOS/qubes-secpack/blob/main/QSBs/qsb-096-2023.txt.sig.marmarek
Simon Gaiser (aka HW42) (https://www.qubes-os.org/team/#simon-gaiser-aka-hw42)’s PGP signature
-----BEGIN PGP SIGNATURE-----
iQIzBAABCgAdFiEE6hjn8EDEHdrv6aoPSsGN4REuFJAFAmVTNYAACgkQSsGN4REu
FJBLqw/8Cq16ZBx7TJnlF4c1NnqJ3EBUf9VNl8/poZEvUKTVV/68UjJa8uEvD7n+
PHgNko7yrNXIRPAS7zLs4w0gtd8vN7COQetARS8QX2YSLoNb+564ElNm8VXxOdKx
eA6xzNUww6javbyoSCPqwMGia2FkAjcjxY5L4CFCjXx+5uS+Qom9+MaTVskroHAZ
dXE37TILGDsTTBQZnX/phPxUZTQK7gIbKwFlrOSmj0QVslHF2/dRNpM3wmEQqhzj
g/vOuA+TO86mW+rrYOHCIJFarAkrOtJQ7RDDNUP2P9hgOxg8qiCchdEMJPiC+uMW
xpZ+XSzjlJSXVlSdg/4Q0ZQ2SxK1he+mTkRBxgjxYfam1JAiTWLDVMxWjH7zvyeH
Ymk92gIfJRcTrdELCY7K6KCBk+y7dIfm47UmyeSmGtRSuhqFvJUvE9GZl2BPUd7f
cejkJCegJ6lxAWxQmzQ0lOq9j0PaqqbxOcIyq+DBaMfDWExKeOvmzajHFKWPUBqs
TpYGSqvVzhkstgqid5t0vR8WbH1GpHRSUo6ytEREkIJ6KShFGeknju60EiRNDEcA
SvFIp01pjzO/q3px3ywNheZ7zNP/B3wr/P2e7U1mxg0sBy4QMQxqsUtscsJZMpZe
hl1XBjqYLpeppAq9kohZUV1H++q1WMxUJ72PXEiX2DRT8RxLl5w=
=ANw6
-----END PGP SIGNATURE-----
Source: https://github.com/QubesOS/qubes-secpack/blob/main/QSBs/qsb-096-2023.txt.sig.simon
What is the purpose of this announcement?
The purpose of this announcement is to inform the Qubes community that a new Qubes security bulletin (QSB) has been published.
What is a Qubes security bulletin (QSB)?
A Qubes security bulletin (QSB) is a security announcement issued by the Qubes security team (https://www.qubes-os.org/security/#qubes-security-team). A QSB typically provides a summary and impact analysis of one or more recently-discovered software vulnerabilities, including details about patching to address them. For a list of all QSBs, see Qubes security bulletins (QSBs) (https://www.qubes-os.org/security/qsb/).
Why should I care about QSBs?
QSBs tell you what actions you must take in order to protect yourself from recently-discovered security vulnerabilities. In most cases, security vulnerabilities are addressed by updating normally (https://www.qubes-os.org/doc/how-to-update/). However, in some cases, special user action is required. In all cases, the required actions are detailed in QSBs.
What are the PGP signatures that accompany QSBs?
A PGP (https://en.wikipedia.org/wiki/Pretty_Good_Privacy) signature is a cryptographic digital signature (https://en.wikipedia.org/wiki/Digital_signature) made in accordance with the OpenPGP (https://en.wikipedia.org/wiki/Pretty_Good_Privacy#OpenPGP) standard. PGP signatures can be cryptographically verified with programs like GNU Privacy Guard (GPG) (https://gnupg.org/). The Qubes security team cryptographically signs all QSBs so that Qubes users have a reliable way to check whether QSBs are genuine. The only way to be certain that a QSB is authentic is by verifying its PGP signatures.
Why should I care whether a QSB is authentic?
A forged QSB could deceive you into taking actions that adversely affect the security of your Qubes OS system, such as installing malware or making configuration changes that render your system vulnerable to attack. Falsified QSBs could sow fear, uncertainty, and doubt about the security of Qubes OS or the status of the Qubes OS Project.
How do I verify the PGP signatures on a QSB?
The following command-line instructions assume a Linux system with git and gpg installed. (For Windows and Mac options, see OpenPGP software (https://www.qubes-os.org/security/verifying-signatures/#openpgp-software).)
Obtain the Qubes Master Signing Key (QMSK), e.g.:
$ gpg --fetch-keys https://keys.qubes-os.org/keys/qubes-master-signing-key.asc
gpg: directory '/home/user/.gnupg' created
gpg: keybox '/home/user/.gnupg/pubring.kbx' created
gpg: requesting key from 'https://keys.qubes-os.org/keys/qubes-master-signing-key.asc'
gpg: /home/user/.gnupg/trustdb.gpg: trustdb created
gpg: key DDFA1A3E36879494: public key "Qubes Master Signing Key" imported
gpg: Total number processed: 1
gpg: imported: 1
(For more ways to obtain the QMSK, see How to import and authenticate the Qubes Master Signing Key (https://www.qubes-os.org/security/verifying-signatures/#how-to-import-and-authenticate-the-qubes-master-signing-key).)
View the fingerprint of the PGP key you just imported. (Note: gpg> indicates a prompt inside of the GnuPG program. Type what appears after it when prompted.)
$ gpg --edit-key 0x427F11FD0FAA4B080123F01CDDFA1A3E36879494
gpg (GnuPG) 2.2.27; Copyright (C) 2021 Free Software Foundation, Inc.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
pub rsa4096/DDFA1A3E36879494
created: 2010-04-01 expires: never usage: SC
trust: unknown validity: unknown
[ unknown] (1). Qubes Master Signing Key
gpg> fpr
pub rsa4096/DDFA1A3E36879494 2010-04-01 Qubes Master Signing Key
Primary key fingerprint: 427F 11FD 0FAA 4B08 0123 F01C DDFA 1A3E 3687 9494
Important: At this point, you still don’t know whether the key you just imported is the genuine QMSK or a forgery. In order for this entire procedure to provide meaningful security benefits, you must authenticate the QMSK out-of-band. Do not skip this step! The standard method is to obtain the QMSK fingerprint from multiple independent sources in several different ways and check to see whether they match the key you just imported. For more information, see How to import and authenticate the Qubes Master Signing Key (https://www.qubes-os.org/security/verifying-signatures/#how-to-import-and-authenticate-the-qubes-master-signing-key).
Tip: After you have authenticated the QMSK out-of-band to your satisfaction, record the QMSK fingerprint in a safe place (or several) so that you don’t have to repeat this step in the future.
Once you are satisfied that you have the genuine QMSK, set its trust level to 5 (“ultimate”), then quit GnuPG with q.
gpg> trust
pub rsa4096/DDFA1A3E36879494
created: 2010-04-01 expires: never usage: SC
trust: unknown validity: unknown
[ unknown] (1). Qubes Master Signing Key
Please decide how far you trust this user to correctly verify other users' keys
(by looking at passports, checking fingerprints from different sources, etc.)
1 = I don't know or won't say
2 = I do NOT trust
3 = I trust marginally
4 = I trust fully
5 = I trust ultimately
m = back to the main menu
Your decision? 5
Do you really want to set this key to ultimate trust? (y/N) y
pub rsa4096/DDFA1A3E36879494
created: 2010-04-01 expires: never usage: SC
trust: ultimate validity: unknown
[ unknown] (1). Qubes Master Signing Key
Please note that the shown key validity is not necessarily correct
unless you restart the program.
gpg> q
Use Git to clone the qubes-secpack repo.
$ git clone https://github.com/QubesOS/qubes-secpack.git
Cloning into 'qubes-secpack'...
remote: Enumerating objects: 4065, done.
remote: Counting objects: 100% (1474/1474), done.
remote: Compressing objects: 100% (742/742), done.
remote: Total 4065 (delta 743), reused 1413 (delta 731), pack-reused 2591
Receiving objects: 100% (4065/4065), 1.64 MiB | 2.53 MiB/s, done.
Resolving deltas: 100% (1910/1910), done.
Import the included PGP keys. (See our PGP key policies (https://www.qubes-os.org/security/pack/#pgp-key-policies) for important information about these keys.)
$ gpg --import qubes-secpack/keys/*/*
gpg: key 063938BA42CFA724: public key "Marek Marczykowski-Górecki (Qubes OS signing key)" imported
gpg: requesting key from 'https://keys.qubes-os.org/keys/qubes-master-signing-key.asc'
gpg: /home/user/.gnupg/trustdb.gpg: trustdb created
gpg: key DDFA1A3E36879494: public key "Qubes Master Signing Key" imported
gpg: Total number processed: 1
gpg: imported: 1
(For more ways to obtain the QMSK, see How to import and authenticate the Qubes Master Signing Key (https://www.qubes-os.org/security/verifying-signatures/#how-to-import-and-authenticate-the-qubes-master-signing-key).)
View the fingerprint of the PGP key you just imported. (Note: gpg> indicates a prompt inside of the GnuPG program. Type what appears after it when prompted.)
$ gpg --edit-key 0x427F11FD0FAA4B080123F01CDDFA1A3E36879494
gpg (GnuPG) 2.2.27; Copyright (C) 2021 Free Software Foundation, Inc.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
pub rsa4096/DDFA1A3E36879494
created: 2010-04-01 expires: never usage: SC
trust: unknown validity: unknown
[ unknown] (1). Qubes Master Signing Key
gpg> fpr
pub rsa4096/DDFA1A3E36879494 2010-04-01 Qubes Master Signing Key
Primary key fingerprint: 427F 11FD 0FAA 4B08 0123 F01C DDFA 1A3E 3687 9494
Important: At this point, you still don’t know whether the key you just imported is the genuine QMSK or a forgery. In order for this entire procedure to provide meaningful security benefits, you must authenticate the QMSK out-of-band. Do not skip this step! The standard method is to obtain the QMSK fingerprint from multiple independent sources in several different ways and check to see whether they match the key you just imported. For more information, see How to import and authenticate the Qubes Master Signing Key (https://www.qubes-os.org/security/verifying-signatures/#how-to-import-and-authenticate-the-qubes-master-signing-key).
Tip: After you have authenticated the QMSK out-of-band to your satisfaction, record the QMSK fingerprint in a safe place (or several) so that you don’t have to repeat this step in the future.
Once you are satisfied that you have the genuine QMSK, set its trust level to 5 (“ultimate”), then quit GnuPG with q.
gpg> trust
pub rsa4096/DDFA1A3E36879494
created: 2010-04-01 expires: never usage: SC
trust: unknown validity: unknown
[ unknown] (1). Qubes Master Signing Key
Please decide how far you trust this user to correctly verify other users' keys
(by looking at passports, checking fingerprints from different sources, etc.)
1 = I don't know or won't say
2 = I do NOT trust
3 = I trust marginally
4 = I trust fully
5 = I trust ultimately
m = back to the main menu
Your decision? 5
Do you really want to set this key to ultimate trust? (y/N) y
pub rsa4096/DDFA1A3E36879494
created: 2010-04-01 expires: never usage: SC
trust: ultimate validity: unknown
[ unknown] (1). Qubes Master Signing Key
Please note that the shown key validity is not necessarily correct
unless you restart the program.
gpg> q
Use Git to clone the qubes-secpack repo.
$ git clone https://github.com/QubesOS/qubes-secpack.git
Cloning into 'qubes-secpack'...
remote: Enumerating objects: 4065, done.
remote: Counting objects: 100% (1474/1474), done.
remote: Compressing objects: 100% (742/742), done.
remote: Total 4065 (delta 743), reused 1413 (delta 731), pack-reused 2591
Receiving objects: 100% (4065/4065), 1.64 MiB | 2.53 MiB/s, done.
Resolving deltas: 100% (1910/1910), done.
Import the included PGP keys. (See our PGP key policies (https://www.qubes-os.org/security/pack/#pgp-key-policies) for important information about these keys.)
$ gpg --import qubes-secpack/keys/*/*
gpg: key 063938BA42CFA724: public key "Marek Marczykowski-Górecki (Qubes OS signing key)" imported
gpg: qubes-secpack/keys/core-devs/retired: read error: Is a directory
gpg: no valid OpenPGP data found.
gpg: key 8C05216CE09C093C: 1 signature not checked due to a missing key
gpg: key 8C05216CE09C093C: public key "HW42 (Qubes Signing Key)" imported
gpg: key DA0434BC706E1FCF: public key "Simon Gaiser (Qubes OS signing key)" imported
gpg: key 8CE137352A019A17: 2 signatures not checked due to missing keys
gpg: key 8CE137352A019A17: public key "Andrew David Wong (Qubes Documentation Signing Key)" imported
gpg: key AAA743B42FBC07A9: public key "Brennan Novak (Qubes Website & Documentation Signing)" imported
gpg: key B6A0BB95CA74A5C3: public key "Joanna Rutkowska (Qubes Documentation Signing Key)" imported
gpg: key F32894BE9684938A: public key "Marek Marczykowski-Górecki (Qubes Documentation Signing Key)" imported
gpg: key 6E7A27B909DAFB92: public key "Hakisho Nukama (Qubes Documentation Signing Key)" imported
gpg: key 485C7504F27D0A72: 1 signature not checked due to a missing key
gpg: key 485C7504F27D0A72: public key "Sven Semmler (Qubes Documentation Signing Key)" imported
gpg: key BB52274595B71262: public key "unman (Qubes Documentation Signing Key)" imported
gpg: key DC2F3678D272F2A8: 1 signature not checked due to a missing key
gpg: key DC2F3678D272F2A8: public key "Wojtek Porczyk (Qubes OS documentation signing key)" imported
gpg: key FD64F4F9E9720C4D: 1 signature not checked due to a missing key
gpg: key FD64F4F9E9720C4D: public key "Zrubi (Qubes Documentation Signing Key)" imported
gpg: key DDFA1A3E36879494: "Qubes Master Signing Key" not changed
gpg: key 1848792F9E2795E9: public key "Qubes OS Release 4 Signing Key" imported
gpg: qubes-secpack/keys/release-keys/retired: read error: Is a directory
gpg: no valid OpenPGP data found.
gpg: key D655A4F21830E06A: public key "Marek Marczykowski-Górecki (Qubes security pack)" imported
gpg: key ACC2602F3F48CB21: public key "Qubes OS Security Team" imported
gpg: qubes-secpack/keys/security-team/retired: read error: Is a directory
gpg: no valid OpenPGP data found.
gpg: key 4AC18DE1112E1490: public key "Simon Gaiser (Qubes Security Pack signing key)" imported
gpg: Total number processed: 17
gpg: imported: 16
gpg: unchanged: 1
gpg: marginals needed: 3 completes needed: 1 trust model: pgp
gpg: depth: 0 valid: 1 signed: 6 trust: 0-, 0q, 0n, 0m, 0f, 1u
gpg: depth: 1 valid: 6 signed: 0 trust: 6-, 0q, 0n, 0m, 0f, 0u
Verify signed Git tags.
$ cd qubes-secpack/
$ git tag -v `git describe`
object 266e14a6fae57c9a91362c9ac784d3a891f4d351
type commit
tag marmarek_sec_266e14a6
tagger Marek Marczykowski-Górecki 1677757924 +0100
Tag for commit 266e14a6fae57c9a91362c9ac784d3a891f4d351
gpg: Signature made Thu 02 Mar 2023 03:52:04 AM PST
gpg: using RSA key 2D1771FE4D767EDC76B089FAD655A4F21830E06A
gpg: Good signature from "Marek Marczykowski-Górecki (Qubes security pack)" [full]
The exact output will differ, but the final line should always start with gpg: Good signature from... followed by an appropriate key. The [full] indicates full trust, which this key inherits in virtue of being validly signed by the QMSK.
Verify PGP signatures, e.g.:
$ cd QSBs/
$ gpg --verify qsb-087-2022.txt.sig.marmarek qsb-087-2022.txt
gpg: Signature made Wed 23 Nov 2022 04:05:51 AM PST
gpg: using RSA key 2D1771FE4D767EDC76B089FAD655A4F21830E06A
gpg: Good signature from "Marek Marczykowski-Górecki (Qubes security pack)" [full]
$ gpg --verify qsb-087-2022.txt.sig.simon qsb-087-2022.txt
gpg: Signature made Wed 23 Nov 2022 03:50:42 AM PST
gpg: using RSA key EA18E7F040C41DDAEFE9AA0F4AC18DE1112E1490
gpg: Good signature from "Simon Gaiser (Qubes Security Pack signing key)" [full]
$ cd ../canaries/
$ gpg --verify canary-034-2023.txt.sig.marmarek canary-034-2023.txt
gpg: Signature made Thu 02 Mar 2023 03:51:48 AM PST
gpg: using RSA key 2D1771FE4D767EDC76B089FAD655A4F21830E06A
gpg: no valid OpenPGP data found.
gpg: key 8C05216CE09C093C: 1 signature not checked due to a missing key
gpg: key 8C05216CE09C093C: public key "HW42 (Qubes Signing Key)" imported
gpg: key DA0434BC706E1FCF: public key "Simon Gaiser (Qubes OS signing key)" imported
gpg: key 8CE137352A019A17: 2 signatures not checked due to missing keys
gpg: key 8CE137352A019A17: public key "Andrew David Wong (Qubes Documentation Signing Key)" imported
gpg: key AAA743B42FBC07A9: public key "Brennan Novak (Qubes Website & Documentation Signing)" imported
gpg: key B6A0BB95CA74A5C3: public key "Joanna Rutkowska (Qubes Documentation Signing Key)" imported
gpg: key F32894BE9684938A: public key "Marek Marczykowski-Górecki (Qubes Documentation Signing Key)" imported
gpg: key 6E7A27B909DAFB92: public key "Hakisho Nukama (Qubes Documentation Signing Key)" imported
gpg: key 485C7504F27D0A72: 1 signature not checked due to a missing key
gpg: key 485C7504F27D0A72: public key "Sven Semmler (Qubes Documentation Signing Key)" imported
gpg: key BB52274595B71262: public key "unman (Qubes Documentation Signing Key)" imported
gpg: key DC2F3678D272F2A8: 1 signature not checked due to a missing key
gpg: key DC2F3678D272F2A8: public key "Wojtek Porczyk (Qubes OS documentation signing key)" imported
gpg: key FD64F4F9E9720C4D: 1 signature not checked due to a missing key
gpg: key FD64F4F9E9720C4D: public key "Zrubi (Qubes Documentation Signing Key)" imported
gpg: key DDFA1A3E36879494: "Qubes Master Signing Key" not changed
gpg: key 1848792F9E2795E9: public key "Qubes OS Release 4 Signing Key" imported
gpg: qubes-secpack/keys/release-keys/retired: read error: Is a directory
gpg: no valid OpenPGP data found.
gpg: key D655A4F21830E06A: public key "Marek Marczykowski-Górecki (Qubes security pack)" imported
gpg: key ACC2602F3F48CB21: public key "Qubes OS Security Team" imported
gpg: qubes-secpack/keys/security-team/retired: read error: Is a directory
gpg: no valid OpenPGP data found.
gpg: key 4AC18DE1112E1490: public key "Simon Gaiser (Qubes Security Pack signing key)" imported
gpg: Total number processed: 17
gpg: imported: 16
gpg: unchanged: 1
gpg: marginals needed: 3 completes needed: 1 trust model: pgp
gpg: depth: 0 valid: 1 signed: 6 trust: 0-, 0q, 0n, 0m, 0f, 1u
gpg: depth: 1 valid: 6 signed: 0 trust: 6-, 0q, 0n, 0m, 0f, 0u
Verify signed Git tags.
$ cd qubes-secpack/
$ git tag -v `git describe`
object 266e14a6fae57c9a91362c9ac784d3a891f4d351
type commit
tag marmarek_sec_266e14a6
tagger Marek Marczykowski-Górecki 1677757924 +0100
Tag for commit 266e14a6fae57c9a91362c9ac784d3a891f4d351
gpg: Signature made Thu 02 Mar 2023 03:52:04 AM PST
gpg: using RSA key 2D1771FE4D767EDC76B089FAD655A4F21830E06A
gpg: Good signature from "Marek Marczykowski-Górecki (Qubes security pack)" [full]
The exact output will differ, but the final line should always start with gpg: Good signature from... followed by an appropriate key. The [full] indicates full trust, which this key inherits in virtue of being validly signed by the QMSK.
Verify PGP signatures, e.g.:
$ cd QSBs/
$ gpg --verify qsb-087-2022.txt.sig.marmarek qsb-087-2022.txt
gpg: Signature made Wed 23 Nov 2022 04:05:51 AM PST
gpg: using RSA key 2D1771FE4D767EDC76B089FAD655A4F21830E06A
gpg: Good signature from "Marek Marczykowski-Górecki (Qubes security pack)" [full]
$ gpg --verify qsb-087-2022.txt.sig.simon qsb-087-2022.txt
gpg: Signature made Wed 23 Nov 2022 03:50:42 AM PST
gpg: using RSA key EA18E7F040C41DDAEFE9AA0F4AC18DE1112E1490
gpg: Good signature from "Simon Gaiser (Qubes Security Pack signing key)" [full]
$ cd ../canaries/
$ gpg --verify canary-034-2023.txt.sig.marmarek canary-034-2023.txt
gpg: Signature made Thu 02 Mar 2023 03:51:48 AM PST
gpg: using RSA key 2D1771FE4D767EDC76B089FAD655A4F21830E06A
gpg: Good signature from "Marek Marczykowski-Górecki (Qubes security pack)" [full]
$ gpg --verify canary-034-2023.txt.sig.simon canary-034-2023.txt
gpg: Signature made Thu 02 Mar 2023 01:47:52 AM PST
gpg: using RSA key EA18E7F040C41DDAEFE9AA0F4AC18DE1112E1490
gpg: Good signature from "Simon Gaiser (Qubes Security Pack signing key)" [full]
Again, the exact output will differ, but the final line of output from each gpg --verify command should always start with gpg: Good signature from... followed by an appropriate key.
For this announcement (QSB-096), the commands are:
$ gpg --verify qsb-096-2023.txt.sig.marmarek qsb-096-2023.txt
$ gpg --verify qsb-096-2023.txt.sig.simon qsb-096-2023.txt
You can also verify the signatures directly from this announcement in addition to or instead of verifying the files from the qubes-secpack. Simply copy and paste the QSB-096 text into a plain text file and do the same for both signature files. Then, perform the same authentication steps as listed above, substituting the filenames above with the names of the files you just created.
$ gpg --verify canary-034-2023.txt.sig.simon canary-034-2023.txt
gpg: Signature made Thu 02 Mar 2023 01:47:52 AM PST
gpg: using RSA key EA18E7F040C41DDAEFE9AA0F4AC18DE1112E1490
gpg: Good signature from "Simon Gaiser (Qubes Security Pack signing key)" [full]
Again, the exact output will differ, but the final line of output from each gpg --verify command should always start with gpg: Good signature from... followed by an appropriate key.
For this announcement (QSB-096), the commands are:
$ gpg --verify qsb-096-2023.txt.sig.marmarek qsb-096-2023.txt
$ gpg --verify qsb-096-2023.txt.sig.simon qsb-096-2023.txt
You can also verify the signatures directly from this announcement in addition to or instead of verifying the files from the qubes-secpack. Simply copy and paste the QSB-096 text into a plain text file and do the same for both signature files. Then, perform the same authentication steps as listed above, substituting the filenames above with the names of the files you just created.
QSB-097: "Reptar" Intel redundant prefix vulnerability
https://www.qubes-os.org/news/2023/11/15/qsb-097/
We have published Qubes Security Bulletin 097: “Reptar” Intel redundant prefix vulnerability (https://github.com/QubesOS/qubes-secpack/blob/main/QSBs/qsb-097-2023.txt). The text of this QSB and its accompanying cryptographic signatures are reproduced below. For an explanation of this announcement and instructions for authenticating this QSB, please see the end of this announcement.
Qubes Security Bulletin 097
---===[ Qubes Security Bulletin 097 ]===---
2023-11-14
"Reptar" Intel redundant prefix vulnerability
(CVE-2023-23583, INTEL-SA-00950)
User action
------------
Continue to update normally [1] in order to receive the security updates
described in the "Patching" section below. No other user action is
required in response to this QSB.
Summary
--------
On 2023-11-14, Intel published INTEL-SA-00950, "2023.4 IPU Out-of-Band
(OOB) - Intel® Processor Advisory" [3] accompanied by advisory guidance
[4] that states:
| Under certain microarchitectural conditions, Intel has identified
| cases where execution of an instruction (REP MOVSB) encoded with a
| redundant REX prefix may result in unpredictable system behavior
| resulting in a system crash/hang, or, in some limited scenarios, may
| allow escalation of privilege (EoP) from CPL3 to CPL0.
This vulnerability has been assigned CVE-2023-23583. [5]
Impact
-------
On affected systems, a qube running in PV mode can attempt to exploit
this vulnerability in order to escalate its privileges to those of dom0.
In the default Qubes OS configuration, the stubdomains for sys-net and
sys-usb run in PV mode. (Dom0 also runs in PV mode, but it is fully
trusted.)
In addition, any qube can attempt to exploit this vulnerability in order
to crash the system, resulting in a denial of service (DoS).
Tavis Ormandy's write-up [6] suggests that disabling hyper-threading
(which Qubes OS does by default) might reduce the impact to that of a
denial-of-service attack, but we cannot completely rule out the
possibility of privilege escalation even with hyper-threading disabled.
Affected systems
-----------------
Only systems with Intel processors are affected, specifically:
- 10th generation Core and newer processors
- Certain server processors
According to Intel, some recent processor families already have
mitigations. For details, see the tables of affected products in
INTEL-SA-00950. [3]
Patching
---------
The following packages contain security updates that address the
vulnerabilities described in this bulletin:
For Qubes 4.1, in dom0:
- microcode_ctl, version 2.1-56.qubes1
For Qubes 4.2, in dom0:
- microcode_ctl, version 2.1-56.qubes1
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. [2] Once available, the packages are to be installed
via the Qubes Update tool or its command-line equivalents. [1]
Dom0 must be restarted afterward in order for the updates to take
effect.
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
initramfs binaries.
Credits
--------
See the Intel security advisory. [3]
References
-----------
[1] https://www.qubes-os.org/doc/how-to-update/
[2] https://www.qubes-os.org/doc/testing/
[3] https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00950.html
[4] https://www.intel.com/content/www/us/en/developer/articles/technical/software-security-guidance/advisory-guidance/redundant-prefix-issue.html
[5] https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-23583
[6] https://lock.cmpxchg8b.com/reptar.html
--
The Qubes Security Team
https://www.qubes-os.org/security/
Source: https://github.com/QubesOS/qubes-secpack/blob/main/QSBs/qsb-097-2023.txt
https://www.qubes-os.org/news/2023/11/15/qsb-097/
We have published Qubes Security Bulletin 097: “Reptar” Intel redundant prefix vulnerability (https://github.com/QubesOS/qubes-secpack/blob/main/QSBs/qsb-097-2023.txt). The text of this QSB and its accompanying cryptographic signatures are reproduced below. For an explanation of this announcement and instructions for authenticating this QSB, please see the end of this announcement.
Qubes Security Bulletin 097
---===[ Qubes Security Bulletin 097 ]===---
2023-11-14
"Reptar" Intel redundant prefix vulnerability
(CVE-2023-23583, INTEL-SA-00950)
User action
------------
Continue to update normally [1] in order to receive the security updates
described in the "Patching" section below. No other user action is
required in response to this QSB.
Summary
--------
On 2023-11-14, Intel published INTEL-SA-00950, "2023.4 IPU Out-of-Band
(OOB) - Intel® Processor Advisory" [3] accompanied by advisory guidance
[4] that states:
| Under certain microarchitectural conditions, Intel has identified
| cases where execution of an instruction (REP MOVSB) encoded with a
| redundant REX prefix may result in unpredictable system behavior
| resulting in a system crash/hang, or, in some limited scenarios, may
| allow escalation of privilege (EoP) from CPL3 to CPL0.
This vulnerability has been assigned CVE-2023-23583. [5]
Impact
-------
On affected systems, a qube running in PV mode can attempt to exploit
this vulnerability in order to escalate its privileges to those of dom0.
In the default Qubes OS configuration, the stubdomains for sys-net and
sys-usb run in PV mode. (Dom0 also runs in PV mode, but it is fully
trusted.)
In addition, any qube can attempt to exploit this vulnerability in order
to crash the system, resulting in a denial of service (DoS).
Tavis Ormandy's write-up [6] suggests that disabling hyper-threading
(which Qubes OS does by default) might reduce the impact to that of a
denial-of-service attack, but we cannot completely rule out the
possibility of privilege escalation even with hyper-threading disabled.
Affected systems
-----------------
Only systems with Intel processors are affected, specifically:
- 10th generation Core and newer processors
- Certain server processors
According to Intel, some recent processor families already have
mitigations. For details, see the tables of affected products in
INTEL-SA-00950. [3]
Patching
---------
The following packages contain security updates that address the
vulnerabilities described in this bulletin:
For Qubes 4.1, in dom0:
- microcode_ctl, version 2.1-56.qubes1
For Qubes 4.2, in dom0:
- microcode_ctl, version 2.1-56.qubes1
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. [2] Once available, the packages are to be installed
via the Qubes Update tool or its command-line equivalents. [1]
Dom0 must be restarted afterward in order for the updates to take
effect.
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
initramfs binaries.
Credits
--------
See the Intel security advisory. [3]
References
-----------
[1] https://www.qubes-os.org/doc/how-to-update/
[2] https://www.qubes-os.org/doc/testing/
[3] https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00950.html
[4] https://www.intel.com/content/www/us/en/developer/articles/technical/software-security-guidance/advisory-guidance/redundant-prefix-issue.html
[5] https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-23583
[6] https://lock.cmpxchg8b.com/reptar.html
--
The Qubes Security Team
https://www.qubes-os.org/security/
Source: https://github.com/QubesOS/qubes-secpack/blob/main/QSBs/qsb-097-2023.txt
Marek Marczykowski-Górecki (https://www.qubes-os.org/team/#marek-marczykowski-g%C3%B3recki)’s PGP signature
-----BEGIN PGP SIGNATURE-----
iQIzBAABCAAdFiEELRdx/k12ftx2sIn61lWk8hgw4GoFAmVUDxMACgkQ1lWk8hgw
4Grl2RAAizymbIDjwL+Al/FkxW6DqJvygG/7aborDLcSgDtE6X4jC2b/drCkI++m
gAnY8xr7D4l+g5/c+G0va8iH6Q3wKm9r9IUyXBB/SlbdziSR2hrgGOPZ7V0mg2zU
60G2lZhwFV0hqEiFLA9TDfD4sL61sP52Jtilvg0n1JjOp2JqQXn0m61+T5m6TdU1
c3N/ajN3H09Fi3x0HNKs2569uK8kI5IQDHG8WQStD2Sr8XnK6M/KOj9u+UxNoYvv
6j7eXlUCjkBWx7yzP1/uP1OuIG589tzRUTAwm+JK0kpYu0hzGgBji+C8vVG4BzFk
+aQJ08UFOO3DCmBhg/swjDoMBmXeEG4ld0uhDrkzwdOP4Wf+mCWGThn8GFNhcLpt
s42vP/KCFIs4xFTcfhjYhpBU3Eym/8b/+64BQoUFS7Pj0kjBdlPADwEkw8cU/Isn
CjescoYD1Irxh9+hm+SRDQq4cJv+h6zQQNznIN1tHiyr+oIeqXzKxV3Q/zxUXmc3
VlbjR5vIPGG7iUjKIPfeZ9fDIVPtt1PiHoQkUX1hNw5+zJ+QUTVHtoUehWif4gL7
RGn1l3IAhLkYrhdrz8iY+YEMe+0/XjkpcpsHoIyhPwhUH4OMBiPkt0zG8LKmnjm0
oDVFYd5d+Dv/kA9A1wjtS9B2r+ydxR5voV+1ke//Fe/JHorDfkE=
=jmq4
-----END PGP SIGNATURE-----
Source: https://github.com/QubesOS/qubes-secpack/blob/main/QSBs/qsb-097-2023.txt.sig.marmarek
Simon Gaiser (aka HW42) (https://www.qubes-os.org/team/#simon-gaiser-aka-hw42)’s PGP signature
-----BEGIN PGP SIGNATURE-----
iQIzBAABCgAdFiEE6hjn8EDEHdrv6aoPSsGN4REuFJAFAmVUvlYACgkQSsGN4REu
FJDMDhAArxzeyHKiTkT/pFcgdgcPxzBahlEZtRH6dmvqs7TdiAh+99RnUpzL8sJH
FZnUg0DYXNTvuhCQ0mJtEb1wzpg4z65FuyJ1NXLzv9qRtmaQeEh7kKX96z6p1Ybt
A2o64GmwX1RFL5tpEhwnCgZ9OTlo2Y2eHq/ra8Y+LBTsFAFN5mhVj7+ElvXnVIQ9
uLUyaH6p+aUPyyoI8zYRYt8fPSJuA+fhYFk97AYYL2LA9ZTTD7QirvUgfeJBQ3PR
XozmcEpKPJb0TpDsOB11muE0C0H9Wdz/artWgqtojqFQ0hiJIEPoKQq9pBqYUJo6
33qVQFvX5pmj2DDx8FEgtt5UuJ+AEtlI3Rh8mSkk49tqwAh1Tg4M2vaECog2HHPO
nqp8jeYulAJn64VMlk4lO3vNMdeWuY3yfJHPszKLvIh2v0IbdmN2r4rooz96vSQ0
FG6MMcdCAr7AVzYGaEoQ6a2LZtaIwvN6DFc99ry04wukWikNfCxXGi1i2F045oFq
lgfB6N0ZdUaLPoghJrhuCQbBBIyYjzBiK0L5P565jhI45xHf9sgYbWtHUAeZEXh0
jsSqgNYWerwO7dz2UKZaDaJCf0KaAan+HEWdcsmAPBKwFZw5yL19Ot6AZCPsFdCc
lY+yvMSxpFZkVZlX31QEuCw/ICuubk92JqTJMw44EmenLqImCmI=
=LP5Z
-----END PGP SIGNATURE-----
Source: https://github.com/QubesOS/qubes-secpack/blob/main/QSBs/qsb-097-2023.txt.sig.simon
What is the purpose of this announcement?
The purpose of this announcement is to inform the Qubes community that a new Qubes security bulletin (QSB) has been published.
What is a Qubes security bulletin (QSB)?
A Qubes security bulletin (QSB) is a security announcement issued by the Qubes security team (https://www.qubes-os.org/security/#qubes-security-team). A QSB typically provides a summary and impact analysis of one or more recently-discovered software vulnerabilities, including details about patching to address them. For a list of all QSBs, see Qubes security bulletins (QSBs) (https://www.qubes-os.org/security/qsb/).
Why should I care about QSBs?
QSBs tell you what actions you must take in order to protect yourself from recently-discovered security vulnerabilities. In most cases, security vulnerabilities are addressed by updating normally (https://www.qubes-os.org/doc/how-to-update/). However, in some cases, special user action is required. In all cases, the required actions are detailed in QSBs.
What are the PGP signatures that accompany QSBs?
A PGP (https://en.wikipedia.org/wiki/Pretty_Good_Privacy) signature is a cryptographic digital signature (https://en.wikipedia.org/wiki/Digital_signature) made in accordance with the OpenPGP (https://en.wikipedia.org/wiki/Pretty_Good_Privacy#OpenPGP) standard. PGP signatures can be cryptographically verified with programs like GNU Privacy Guard (GPG) (https://gnupg.org/). The Qubes security team cryptographically signs all QSBs so that Qubes users have a reliable way to check whether QSBs are genuine. The only way to be certain that a QSB is authentic is by verifying its PGP signatures.
Why should I care whether a QSB is authentic?
-----BEGIN PGP SIGNATURE-----
iQIzBAABCAAdFiEELRdx/k12ftx2sIn61lWk8hgw4GoFAmVUDxMACgkQ1lWk8hgw
4Grl2RAAizymbIDjwL+Al/FkxW6DqJvygG/7aborDLcSgDtE6X4jC2b/drCkI++m
gAnY8xr7D4l+g5/c+G0va8iH6Q3wKm9r9IUyXBB/SlbdziSR2hrgGOPZ7V0mg2zU
60G2lZhwFV0hqEiFLA9TDfD4sL61sP52Jtilvg0n1JjOp2JqQXn0m61+T5m6TdU1
c3N/ajN3H09Fi3x0HNKs2569uK8kI5IQDHG8WQStD2Sr8XnK6M/KOj9u+UxNoYvv
6j7eXlUCjkBWx7yzP1/uP1OuIG589tzRUTAwm+JK0kpYu0hzGgBji+C8vVG4BzFk
+aQJ08UFOO3DCmBhg/swjDoMBmXeEG4ld0uhDrkzwdOP4Wf+mCWGThn8GFNhcLpt
s42vP/KCFIs4xFTcfhjYhpBU3Eym/8b/+64BQoUFS7Pj0kjBdlPADwEkw8cU/Isn
CjescoYD1Irxh9+hm+SRDQq4cJv+h6zQQNznIN1tHiyr+oIeqXzKxV3Q/zxUXmc3
VlbjR5vIPGG7iUjKIPfeZ9fDIVPtt1PiHoQkUX1hNw5+zJ+QUTVHtoUehWif4gL7
RGn1l3IAhLkYrhdrz8iY+YEMe+0/XjkpcpsHoIyhPwhUH4OMBiPkt0zG8LKmnjm0
oDVFYd5d+Dv/kA9A1wjtS9B2r+ydxR5voV+1ke//Fe/JHorDfkE=
=jmq4
-----END PGP SIGNATURE-----
Source: https://github.com/QubesOS/qubes-secpack/blob/main/QSBs/qsb-097-2023.txt.sig.marmarek
Simon Gaiser (aka HW42) (https://www.qubes-os.org/team/#simon-gaiser-aka-hw42)’s PGP signature
-----BEGIN PGP SIGNATURE-----
iQIzBAABCgAdFiEE6hjn8EDEHdrv6aoPSsGN4REuFJAFAmVUvlYACgkQSsGN4REu
FJDMDhAArxzeyHKiTkT/pFcgdgcPxzBahlEZtRH6dmvqs7TdiAh+99RnUpzL8sJH
FZnUg0DYXNTvuhCQ0mJtEb1wzpg4z65FuyJ1NXLzv9qRtmaQeEh7kKX96z6p1Ybt
A2o64GmwX1RFL5tpEhwnCgZ9OTlo2Y2eHq/ra8Y+LBTsFAFN5mhVj7+ElvXnVIQ9
uLUyaH6p+aUPyyoI8zYRYt8fPSJuA+fhYFk97AYYL2LA9ZTTD7QirvUgfeJBQ3PR
XozmcEpKPJb0TpDsOB11muE0C0H9Wdz/artWgqtojqFQ0hiJIEPoKQq9pBqYUJo6
33qVQFvX5pmj2DDx8FEgtt5UuJ+AEtlI3Rh8mSkk49tqwAh1Tg4M2vaECog2HHPO
nqp8jeYulAJn64VMlk4lO3vNMdeWuY3yfJHPszKLvIh2v0IbdmN2r4rooz96vSQ0
FG6MMcdCAr7AVzYGaEoQ6a2LZtaIwvN6DFc99ry04wukWikNfCxXGi1i2F045oFq
lgfB6N0ZdUaLPoghJrhuCQbBBIyYjzBiK0L5P565jhI45xHf9sgYbWtHUAeZEXh0
jsSqgNYWerwO7dz2UKZaDaJCf0KaAan+HEWdcsmAPBKwFZw5yL19Ot6AZCPsFdCc
lY+yvMSxpFZkVZlX31QEuCw/ICuubk92JqTJMw44EmenLqImCmI=
=LP5Z
-----END PGP SIGNATURE-----
Source: https://github.com/QubesOS/qubes-secpack/blob/main/QSBs/qsb-097-2023.txt.sig.simon
What is the purpose of this announcement?
The purpose of this announcement is to inform the Qubes community that a new Qubes security bulletin (QSB) has been published.
What is a Qubes security bulletin (QSB)?
A Qubes security bulletin (QSB) is a security announcement issued by the Qubes security team (https://www.qubes-os.org/security/#qubes-security-team). A QSB typically provides a summary and impact analysis of one or more recently-discovered software vulnerabilities, including details about patching to address them. For a list of all QSBs, see Qubes security bulletins (QSBs) (https://www.qubes-os.org/security/qsb/).
Why should I care about QSBs?
QSBs tell you what actions you must take in order to protect yourself from recently-discovered security vulnerabilities. In most cases, security vulnerabilities are addressed by updating normally (https://www.qubes-os.org/doc/how-to-update/). However, in some cases, special user action is required. In all cases, the required actions are detailed in QSBs.
What are the PGP signatures that accompany QSBs?
A PGP (https://en.wikipedia.org/wiki/Pretty_Good_Privacy) signature is a cryptographic digital signature (https://en.wikipedia.org/wiki/Digital_signature) made in accordance with the OpenPGP (https://en.wikipedia.org/wiki/Pretty_Good_Privacy#OpenPGP) standard. PGP signatures can be cryptographically verified with programs like GNU Privacy Guard (GPG) (https://gnupg.org/). The Qubes security team cryptographically signs all QSBs so that Qubes users have a reliable way to check whether QSBs are genuine. The only way to be certain that a QSB is authentic is by verifying its PGP signatures.
Why should I care whether a QSB is authentic?
A forged QSB could deceive you into taking actions that adversely affect the security of your Qubes OS system, such as installing malware or making configuration changes that render your system vulnerable to attack. Falsified QSBs could sow fear, uncertainty, and doubt about the security of Qubes OS or the status of the Qubes OS Project.
How do I verify the PGP signatures on a QSB?
The following command-line instructions assume a Linux system with git and gpg installed. (For Windows and Mac options, see OpenPGP software (https://www.qubes-os.org/security/verifying-signatures/#openpgp-software).)
Obtain the Qubes Master Signing Key (QMSK), e.g.:
$ gpg --fetch-keys https://keys.qubes-os.org/keys/qubes-master-signing-key.asc
gpg: directory '/home/user/.gnupg' created
gpg: keybox '/home/user/.gnupg/pubring.kbx' created
gpg: requesting key from 'https://keys.qubes-os.org/keys/qubes-master-signing-key.asc'
gpg: /home/user/.gnupg/trustdb.gpg: trustdb created
gpg: key DDFA1A3E36879494: public key "Qubes Master Signing Key" imported
gpg: Total number processed: 1
gpg: imported: 1
(For more ways to obtain the QMSK, see How to import and authenticate the Qubes Master Signing Key (https://www.qubes-os.org/security/verifying-signatures/#how-to-import-and-authenticate-the-qubes-master-signing-key).)
View the fingerprint of the PGP key you just imported. (Note: gpg> indicates a prompt inside of the GnuPG program. Type what appears after it when prompted.)
$ gpg --edit-key 0x427F11FD0FAA4B080123F01CDDFA1A3E36879494
gpg (GnuPG) 2.2.27; Copyright (C) 2021 Free Software Foundation, Inc.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
pub rsa4096/DDFA1A3E36879494
created: 2010-04-01 expires: never usage: SC
trust: unknown validity: unknown
[ unknown] (1). Qubes Master Signing Key
gpg> fpr
pub rsa4096/DDFA1A3E36879494 2010-04-01 Qubes Master Signing Key
Primary key fingerprint: 427F 11FD 0FAA 4B08 0123 F01C DDFA 1A3E 3687 9494
Important: At this point, you still don’t know whether the key you just imported is the genuine QMSK or a forgery. In order for this entire procedure to provide meaningful security benefits, you must authenticate the QMSK out-of-band. Do not skip this step! The standard method is to obtain the QMSK fingerprint from multiple independent sources in several different ways and check to see whether they match the key you just imported. For more information, see How to import and authenticate the Qubes Master Signing Key (https://www.qubes-os.org/security/verifying-signatures/#how-to-import-and-authenticate-the-qubes-master-signing-key).
Tip: After you have authenticated the QMSK out-of-band to your satisfaction, record the QMSK fingerprint in a safe place (or several) so that you don’t have to repeat this step in the future.
Once you are satisfied that you have the genuine QMSK, set its trust level to 5 (“ultimate”), then quit GnuPG with q.
gpg> trust
pub rsa4096/DDFA1A3E36879494
created: 2010-04-01 expires: never usage: SC
trust: unknown validity: unknown
[ unknown] (1). Qubes Master Signing Key
Please decide how far you trust this user to correctly verify other users' keys
(by looking at passports, checking fingerprints from different sources, etc.)
1 = I don't know or won't say
2 = I do NOT trust
3 = I trust marginally
4 = I trust fully
5 = I trust ultimately
m = back to the main menu
Your decision? 5
Do you really want to set this key to ultimate trust? (y/N) y
pub rsa4096/DDFA1A3E36879494
created: 2010-04-01 expires: never usage: SC
trust: ultimate validity: unknown
[ unknown] (1). Qubes Master Signing Key
Please note that the shown key validity is not necessarily correct
unless you restart the program.
gpg> q
How do I verify the PGP signatures on a QSB?
The following command-line instructions assume a Linux system with git and gpg installed. (For Windows and Mac options, see OpenPGP software (https://www.qubes-os.org/security/verifying-signatures/#openpgp-software).)
Obtain the Qubes Master Signing Key (QMSK), e.g.:
$ gpg --fetch-keys https://keys.qubes-os.org/keys/qubes-master-signing-key.asc
gpg: directory '/home/user/.gnupg' created
gpg: keybox '/home/user/.gnupg/pubring.kbx' created
gpg: requesting key from 'https://keys.qubes-os.org/keys/qubes-master-signing-key.asc'
gpg: /home/user/.gnupg/trustdb.gpg: trustdb created
gpg: key DDFA1A3E36879494: public key "Qubes Master Signing Key" imported
gpg: Total number processed: 1
gpg: imported: 1
(For more ways to obtain the QMSK, see How to import and authenticate the Qubes Master Signing Key (https://www.qubes-os.org/security/verifying-signatures/#how-to-import-and-authenticate-the-qubes-master-signing-key).)
View the fingerprint of the PGP key you just imported. (Note: gpg> indicates a prompt inside of the GnuPG program. Type what appears after it when prompted.)
$ gpg --edit-key 0x427F11FD0FAA4B080123F01CDDFA1A3E36879494
gpg (GnuPG) 2.2.27; Copyright (C) 2021 Free Software Foundation, Inc.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
pub rsa4096/DDFA1A3E36879494
created: 2010-04-01 expires: never usage: SC
trust: unknown validity: unknown
[ unknown] (1). Qubes Master Signing Key
gpg> fpr
pub rsa4096/DDFA1A3E36879494 2010-04-01 Qubes Master Signing Key
Primary key fingerprint: 427F 11FD 0FAA 4B08 0123 F01C DDFA 1A3E 3687 9494
Important: At this point, you still don’t know whether the key you just imported is the genuine QMSK or a forgery. In order for this entire procedure to provide meaningful security benefits, you must authenticate the QMSK out-of-band. Do not skip this step! The standard method is to obtain the QMSK fingerprint from multiple independent sources in several different ways and check to see whether they match the key you just imported. For more information, see How to import and authenticate the Qubes Master Signing Key (https://www.qubes-os.org/security/verifying-signatures/#how-to-import-and-authenticate-the-qubes-master-signing-key).
Tip: After you have authenticated the QMSK out-of-band to your satisfaction, record the QMSK fingerprint in a safe place (or several) so that you don’t have to repeat this step in the future.
Once you are satisfied that you have the genuine QMSK, set its trust level to 5 (“ultimate”), then quit GnuPG with q.
gpg> trust
pub rsa4096/DDFA1A3E36879494
created: 2010-04-01 expires: never usage: SC
trust: unknown validity: unknown
[ unknown] (1). Qubes Master Signing Key
Please decide how far you trust this user to correctly verify other users' keys
(by looking at passports, checking fingerprints from different sources, etc.)
1 = I don't know or won't say
2 = I do NOT trust
3 = I trust marginally
4 = I trust fully
5 = I trust ultimately
m = back to the main menu
Your decision? 5
Do you really want to set this key to ultimate trust? (y/N) y
pub rsa4096/DDFA1A3E36879494
created: 2010-04-01 expires: never usage: SC
trust: ultimate validity: unknown
[ unknown] (1). Qubes Master Signing Key
Please note that the shown key validity is not necessarily correct
unless you restart the program.
gpg> q