• teawrecks@sopuli.xyz
    link
    fedilink
    arrow-up
    7
    ·
    edit-2
    1 year ago

    You’re still going to need them to sign your binary for the console to recognize it as legit.

    Circumventing the official path worked back in the 80s and 90s, but modern consoles and their SDKs were designed with those lessons in mind.

    • 520@kbin.social
      link
      fedilink
      arrow-up
      4
      ·
      edit-2
      1 year ago

      It’s still valuable information for those that would seek to load homebrew (unsigned code) onto their systems.

      Console security is one of those things where every additional barrier helps. The goal isn’t to outright prevent homebrew or piracy but to limit the scope of breaches and delay them as much as possible. Even modern consoles like the Switch and PS5 are not immune

      • teawrecks@sopuli.xyz
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        It would be great if there was a guaranteed way to homebrew your consoles, but yeah security and stability is the real thing we benefit from. I don’t think anyone would advocate for more hackers in console multiplayer games, and I don’t want a homebrew game I’m running to crash or brick my system because of their fly-by-night hardware usage.

        • 520@kbin.social
          link
          fedilink
          arrow-up
          1
          ·
          edit-2
          1 year ago

          So, I didn’t bring up Xbox earlier, because Microsoft has an official way to run homebrew on Xbox consoles.

          All modern Xboxes have access to something called developer mode. This allows people to put whatever code they like on it, but removes the ability to play retail games. The change isn’t permanent, however, and switching between the modes is perfectly safe.

          This is a big part of the reason why Xbox 1 never had piracy; pirates couldn’t piggyback on the back of homebrewers, who simply opted to use developer mode instead of cracking the console.