:: Re: [DNG] systemd-udevd: renamed ne…
Top Page
Delete this message
Reply to this message
Author: Tobias Hunger
Date:  
To: Dr. Nikolaus Klepp, arnt
CC: dng
Subject: Re: [DNG] systemd-udevd: renamed network interface eth0 to eth1
On Oct 21, 2017 10:05, "Dr. Nikolaus Klepp" <dr.klepp@???> wrote:

> Tobias, until I read your posting a couple of days ago I did not realise
> that UEFI/Secure Boot can be configured such that ONLY my kernels can be
> booted, not even fresh install media from the vendor. Thank you very much.
>
> Arnt


Well, that's not true: If you are lucky, your vendor installed a bios that
allows you seamingly do so. But most likely he didn't. Most likely his
implementation has a backdoor for windows. You'll need to see his contracts
with M$ to verify this. Sometimes somebody down the sales lane will give
you some hints, but don't count on it.


Sure, vendor sell crappy firmware, nothing new there. You have the same
problem with any firmware, this is in no way limited to UEFI.

It is also pretty easy to test for: Remove the Microsoft key and boot a
Windows install CD. If that still boots, then the UEFI implementation sucks
and you should complain to your vendor. I never had that happen though.

Best Regards,
Tobias