Am Sonntag, 31. Juli 2016 01:22:48 UTC+2 schrieb Andrew David Wong:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> On 2016-07-30 16:06, Fabian Wloch wrote:
> > Am Samstag, 30. Juli 2016 23:25:05 UTC+2 schrieb Markus Kilås:
> >> On 07/30/2016 06:25 PM, Fabian Wloch wrote: The issues with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2016-07-30 16:06, Fabian Wloch wrote:
> Am Samstag, 30. Juli 2016 23:25:05 UTC+2 schrieb Markus Kilås:
>> On 07/30/2016 06:25 PM, Fabian Wloch wrote: The issues with unprotected
>> /boot and BIOS is briefly mentioned on the below link and it
On 07/30/2016 09:24 PM, Markus Kilås wrote:
> On 07/30/2016 06:25 PM, Fabian Wloch wrote:
>> didn't found anything
> The issues with unprotected /boot and BIOS is briefly mentioned on the
> below link and it sounds like AEM should be able to at least be able to
> detect a compromise for you:
>
>
On 07/30/2016 06:25 PM, Fabian Wloch wrote:
> didn't found anything
The issues with unprotected /boot and BIOS is briefly mentioned on the
below link and it sounds like AEM should be able to at least be able to
detect a compromise for you:
https://www.qubes-os.org/doc/multiboot/
Cheers,
Markus
Hello,
there are plenty threads of people asking for advice for dual boot, but this is
not my intention here.
What I would like to know is, what are the risks of a Qubes-Dualboot System?
Let's assume I have installed the latest version of Qubes, Encrypted the whole
drive using LUKS (and a 32
