Readme updated today:

This repository is no longer actively maintained.  

The TrueNAS build system previously hosted here has been moved to an internal infrastructure. This transition was necessary to meet new security requirements, including support for Secure Boot and related platform integrity features that require tighter control over the build and signing pipeline.  

No further updates, pull requests, or issues will be accepted. Existing content is preserved here for historical reference only.  

https://github.com/truenas/scale-build

Wondering if this is just the first step towards doing a minio in the future.

  • frongt@lemmy.zip
    link
    fedilink
    English
    arrow-up
    9
    arrow-down
    1
    ·
    19 hours ago

    It can be a bit of both.

    I don’t think secureboot is an attack on freedom exactly (and it’s certainly not an instance of EEE), but I definitely think it shouldn’t be Microsoft holding the keys.

    • hoshikarakitaridia@lemmy.world
      link
      fedilink
      English
      arrow-up
      9
      ·
      17 hours ago

      Literally today Chris Titus released a video where he emphasized that no one should be using secure boot because the default backend is Microsoft and no one changes their secure boot config.

      If that’s true there’s an argument that the name “secure boot” is hardly detachable from the defaults and thus that name is kid of burnt and shouldn’t be recommended out of an abundance of caution for new users.

      • deafboy@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        arrow-down
        1
        ·
        edit-2
        5 hours ago

        So… nobody changes the default settings, therefore everyone should change the default settings… to the wrong option?

        edit: Why is it that homo sapiens is always willing to go an extra mile just to hurt itself?