• @[email protected]
    link
    fedilink
    English
    121 month ago

    Probably wiping process control code from the systems that contain tons of fiddly hard to find constants and other information.

    • @[email protected]
      link
      fedilink
      English
      111 month ago

      Well that’s less fun than detcord or mission impossible style self-immolating electronics.

    • KillingTimeItself
      link
      fedilink
      English
      31 month ago

      i wonder if this also includes trying to physically damage the machinery in order to ensure one hell of a time getting it back online, because theoretically once you wipe it, you can just start smashing shit together that shouldn’t be smashed together lol.

      • @[email protected]
        link
        fedilink
        English
        31 month ago

        What would be better is polluting the software with invalid but still plausible constraints, so the chips would seem OK and might work for days or weeks but would fail in the field… especially if these chips are used in weapon systems or critical infrastructure.

        • KillingTimeItself
          link
          fedilink
          English
          21 month ago

          this is, decent. The problem here is that it’s almost always easier to reverse engineer a system that’s partially constructed, than it is one that’s completely deconstructed.

          You would ideally want to delete ALL software, and ALL hardware running that software, that would be MUCH harder to reverse engineer. Or at the very least, significantly more expensive.

          although i imagine building chips to fail is almost an impossible thing. Cpus almost never die, unless you blow them up with too much power lol.