-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Thu, Nov 14, 2019 at 10:10:56PM +, Davíð Steinn Geirsson wrote:
> I'm trying to build a R4.0 fc30 template in dispvm, but it fails
> at the "make build-id" step because the lost+found directory is
> in the way.
>
> My build steps:
> * Clone h
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I'm trying to build a R4.0 fc30 template in dispvm, but it fails
at the "make build-id" step because the lost+found directory is
in the way.
My build steps:
* Clone https://github.com/QubesOS/qubes-builder
* cp example-configs/qubes-os-r4.0.conf bui
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Dear Qubes Community,
We have just published Qubes Security Bulletin (QSB) #053: TSX
Asynchronous Abort speculative side channel (XSA-305). The text of this
QSB is reproduced below. This QSB and its accompanying signatures will
always be available i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Dear Qubes Community,
The Xen Project has published Xen Security Advisory 304 (XSA-304).
This XSA does *not* affect the security of Qubes OS, and no user
action is necessary.
This XSA has been added to the XSA Tracker:
https://www.qubes-os.org/sec
Please read these requirements before jumping into suggesting new hardware:
https://www.qubes-os.org/doc/certified-hardware/#hardware-certification-process
btw Intel and AMD two faces for the same coin both of them dirty
organizations.
Chris Laprise:
> I suggest that the Qubes project certify so
I suggest that the Qubes project certify some AMD systems to give users
a more meaningful variety in their available hardware. Currently there
is only the Insurgo X230 plus whichever gen of Thinkpad X1 the devs are
currently using, all of which are based on Intel processors.
The following post
