• CallMeAnAI@lemmy.world
    link
    fedilink
    English
    arrow-up
    5
    arrow-down
    52
    ·
    4 days ago

    (x) doubt.

    I’m not watching this dumb video to find out about every edge case is being exploited.

    • Aielman15@lemmy.worldOP
      link
      fedilink
      English
      arrow-up
      42
      arrow-down
      2
      ·
      edit-2
      4 days ago

      It’s not a dumb video and it’s not an edge case. It’s a great video that goes straight to the point, has timestamps, explains in detail how the exploit works and how consistently, and showcases it.

      The exploit is BadUpdate v1.2, an evolution of the previously known BadUpdate, which was great as a proof of concept but not very useful in practice, as it required an average of 30 minutes to work, had a success rate of about 30%, and needed to be applied every time the console was rebooted (on a console with no sleep mode, may I add).

      By comparison, as shown in the dumb video, the new version of BadUpdate works flawlessly in about a minute (10 max), and has a far greater success rate of about 80%, according to the creator. It can be launched from a USB stick and requires no additional software or hardware modification to the console, and most importantly, works on all X360 and not just earlier editions.

      If you’re too lazy to click on a link, fine, but I’d suggest at least not acting so confidently when saying things you know nothing about.

      • AnUnusualRelic@lemmy.world
        link
        fedilink
        English
        arrow-up
        8
        ·
        4 days ago

        It’s strange that console exploits wouldn’t work consistently on identical hardware with identical firmware. What is it that makes it fail so often?

        • Aielman15@lemmy.worldOP
          link
          fedilink
          English
          arrow-up
          21
          ·
          4 days ago

          Quoting from the GitHub’s page:

          The exploit is a race condition that requires precise timing and several other conditions to be met for it to trigger successfully. As such it can take a while for that to happen.

          Which means that, sometimes, you run the code but it simply fails. When it happens, you can turn off the console and try again.

        • DevCuber@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          7
          ·
          4 days ago

          If i remember correctly, some memory address that needs to be overridden by the exploit is randomized on startup. The only way to find it is to just write to a random address, which often fails

        • Aielman15@lemmy.worldOP
          link
          fedilink
          English
          arrow-up
          2
          ·
          3 days ago

          You should re-read the discussion, because I’m pretty positive you didn’t even get the topic.

          We are talking about being able to play pirated games and homebrew apps on the X360. Of course that doesn’t happen in the wild. Unless you think that I woke up one day with a modded PS1.