• matlag@sh.itjust.works
      link
      fedilink
      arrow-up
      1
      ·
      10 months ago

      In theory, yes, you could make a mess, and any firmware is supposed to be certified to allow the device to be used.

      In practice, this has been a convenient excuse to keep a whole chip with a separate OS in every smartphone, and it is very difficult to isolate from the rest of the system (see Graphene OS efforts).

      I say all firmware should be opensource. Whether you’re allowed to change them or not is a separate question… for now.

      • jpeps@lemmy.world
        link
        fedilink
        arrow-up
        0
        ·
        10 months ago

        In additional to the other comment, I think there’s also a traditional fear of corruption in open source. If the code is public then malicious parties are free to read and take advantage of holes in the security. Secondly it would be possible to contribute code with secret functionality that goes unnoticed. These are fairly easily debunked but seem to remain in people’s heads.

        • blackbelt352@lemmy.world
          link
          fedilink
          arrow-up
          1
          ·
          10 months ago

          Ugh I hate these arguments about giving bad actors easier access. Bad actors are going to figure out flaws and security holes whether it’s open source or not. Security through obfuscation is a temporary measure and having more eyes on the source means more chances for good actors to find flaws and publicize them for fixes.