Most active commenters

    ←back to thread

    253 points pabs3 | 17 comments | | HN request time: 1.233s | source | bottom
    1. jmclnx ◴[] No.44615067[source]
    And this is why I avoid and will always avoid "Secure Boot". I can see many newer Linux people being locked out starting in Sept.
    replies(3): >>44615474 #>>44616122 #>>44617464 #
    2. craftkiller ◴[] No.44615474[source]
    Or you could just remove microsoft's keys from your systems and sign your bootloader with your own key. That's what I do on all of my systems so I am unimpacted by this.
    replies(3): >>44615574 #>>44616310 #>>44616568 #
    3. ekianjo ◴[] No.44615574[source]
    do you have any source on how to do that?
    replies(2): >>44615682 #>>44615805 #
    4. craftkiller ◴[] No.44615682{3}[source]
    I followed https://github.com/nix-community/lanzaboote/blob/master/docs... but naturally you don't want to include the `--microsoft` flag when running `sbctl enroll-keys` if you want to avoid microsoft keys. Also Lanzaboote is only for NixOS.
    5. marcthe12 ◴[] No.44615805{3}[source]
    The arch wiki has the best source https://wiki.archlinux.org/title/Unified_Extensible_Firmware...

    Note sbctl is one of the easier tools to do this.

    6. willa_bombadier ◴[] No.44616122[source]
    There should be some “Sane Usage” certification that a device doesn’t do secure boot, provides fully open and self-maintainable hardware, is independent of all external entities for ongoing use, provides hardware switches to turn off built-ins like ports, mics, and cameras, for power-savings and security.
    replies(2): >>44616412 #>>44616647 #
    7. josephcsible ◴[] No.44616310[source]
    Sure, but that's a lot more work than just disabling Secure Boot, and for most people's threat models, there's zero actual security benefit gained in return.
    replies(1): >>44616363 #
    8. ◴[] No.44616363{3}[source]
    9. pydry ◴[] No.44616412[source]
    "Will this piss off or delight Microsoft?" is probably a thought that goes through the heads of many OEMs when they decide how to design their machines.
    replies(1): >>44616593 #
    10. brudgers ◴[] No.44616568[source]
    Warning: Replacing the platform keys with your own can end up bricking hardware on some machines, including laptops, making it impossible to get into the firmware settings to rectify the situation. This is due to the fact that some device (e.g GPU) firmware (OpROMs), that get executed during boot, are signed using Microsoft 3rd Party UEFI CA certificate or vendor certificates. This is the case in many Lenovo Thinkpad X, P and T series laptops which uses the Lenovo CA certificate to sign UEFI applications and firmware.

    “Just” is doing a lot of heavy lifting in that solution.

    https://wiki.archlinux.org/title/Unified_Extensible_Firmware...

    11. msgodel ◴[] No.44616593{3}[source]
    Weirdly Microsoft has been one of the companies ensuring Linux remains bootable on PCs.
    replies(2): >>44616764 #>>44616860 #
    12. bayindirh ◴[] No.44616647[source]
    To be able to get Windows licenses and preload Windows on your system, put that little Windows sticker and sell your machine to the masses, you need a Windows Compatibility certificate, and that certificate needs you to have Secure Boot and enabled by default.
    replies(1): >>44616696 #
    13. salawat ◴[] No.44616696{3}[source]
    Sounds anti-competitive as fuck to me. Maybe we should, I don't know; do something about companies using contractual requirements to lock key industrial into one way of doing things in order to shut down such efforts?
    replies(1): >>44617086 #
    14. bayindirh ◴[] No.44616764{4}[source]
    Bill Gates famously asked: "Can we create a standard or expand something like ACPI, so Linux becomes unbootable on PCs?"

    So, believing this is very, very hard.

    15. pydry ◴[] No.44616860{4}[source]
    Microsoft has been trying to tread a fine line between exerting subtle pressure on OEMs to make Linux annoying to boot so it doesnt become more popular and not violating the terms of its antitrust agreement.
    16. edoceo ◴[] No.44617086{4}[source]
    What is the something we can do?
    17. lexicality ◴[] No.44617464[source]
    Newer Linux people will presumably be using the new key though?