4 ms·
> "But, you're scaremongering! See, I put this Debian USB pendrive in, hit F1, hit cursor down three times, tab, down five times, space, F12, and I can still bo
by Avamander 4y ago
> "But, you're scaremongering! See, I put this Debian USB pendrive in, hit F1, hit cursor down three times, tab, down five times, space, F12, and I can still boot it fine!"
Because yes, one extra option in UEFI settings is the end of Linux on the Desktop. People definitely do not change anything else in UEFI settings ever as Linux users and it's significantly more complex than before. /s
But that's not true, is it? Changing DG or SB toggle is no more difficult than setting the system's clock or boot order. These things are also described in the manual. People installing any OS fresh are likely to have the skillset necessary to do so.
> Back when all this Secure Boot was announced, we already said that its main purpose seemed to be to make booting of non-MS operating systems more complicated, rather than security enforcement.
This is not Secure Boot per se, it is Device Guard. It's quite misleading to call it Secure Boot. If you read up on what Device Guard tries to achieve you should be able to see how it as a whole does provide noteworthy security improvements.
> Now, your Debian pendrive will not boot on this Lenovo PC, even if MS-signed.
*Please* do go on how you're not scaremongering here or in the previous thread. That sentence is literally false.
- AshamedCaptain 4y ago> This is not Secure Boot per se, it is Device Guard. It's quite misleading to call it Secure Boot. If you read up on what Device Guard tries to achieve on Secured Core PC As clearly mentioned in the TFA, this is Secure Boot itself and has nothing to do with Device Guard.
- Avamander 4y agoYeah and it is incorrect. Disabling that CA is a part of Device Guard requirements since 2016. Obviously Secure Boot enforces its configuration, but it's specified and set as such due to Device Guard.