-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Mon, Aug 15, 2016 at 11:06:32AM +0200, Joanna Rutkowska wrote:
> On Sun, Aug 14, 2016 at 12:55:10PM -0700, el...@tutanota.com wrote:
> > Just to clarify, that means that even if the UEFI is exploited, it does not
> > matter with Qubes?
>
> Yes.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sun, Aug 14, 2016 at 12:55:10PM -0700, el...@tutanota.com wrote:
> Just to clarify, that means that even if the UEFI is exploited, it does not
> matter with Qubes?
Yes. Unless the isolation-provider that Qubes happens to be using -- currently
X
Just to clarify, that means that even if the UEFI is exploited, it does not
matter with Qubes?
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to qubes-users+unsu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2016-08-13 20:57, el...@tutanota.com wrote:
> Maybe this is a dumb question, but I can't seem to find any threads here on
> thinkpwn on the qubes group. Should we be turning off our thinkpwn'd
> computers off until there are bios updates to correc
Maybe this is a dumb question, but I can't seem to find any threads here on
thinkpwn on the qubes group.
Should we be turning off our thinkpwn'd computers off until there are bios
updates to correct thinkpwn?
Specifically, if we have...
single boot qubes?
dual boot with some other os (windows
