• BassTurd@lemmy.world
    link
    fedilink
    English
    arrow-up
    9
    ·
    3 hours ago

    I don’t really understand why voting machines are complicated enough that there are feasible vulnerabilities. They have one job, and it’s to count. It really shouldn’t be too tough for a crack team of competent devs to write the software required to make them work securely. No network access, a memory safe language, and strict business rules should be relatively trivial to setup. Double that will external audits and you’ve got yourself a stew.

  • NOT_RICK@lemmy.world
    link
    fedilink
    English
    arrow-up
    54
    ·
    6 hours ago

    The likely motive:

    “My thought was they could keep it in their back pocket to invalidate any [election] results they don’t like,” one of the former officials told ProPublica. “This goes against everything CISA represents.”

    • LillyPip@lemmy.ca
      link
      fedilink
      English
      arrow-up
      11
      ·
      5 hours ago

      Well, this and to exploit them. Like:

      Step 1: exploit vulnerabilities.
      Step 2: accuse opponent of exploiting them, lock them up.
      Step 3: profit

    • artyom@piefed.social
      link
      fedilink
      English
      arrow-up
      15
      arrow-down
      1
      ·
      5 hours ago

      Well that was…unexpected. Surely the more likely scenario is that they exploit the hack to change the results?

      • FrostyTheDoo@lemmy.world
        link
        fedilink
        English
        arrow-up
        16
        ·
        5 hours ago

        That’s a much more findable paper trail than “holy shit we just found a vulnerability we didn’t know about, that means someone might have cheated so we have to invalidate the results”

        Instead of “whoopsie this thing says I won even though everyone you talk to says they voted against me”

  • FauxLiving@lemmy.world
    link
    fedilink
    English
    arrow-up
    9
    ·
    5 hours ago

    Do vulnerabilities in voting software typically get disclosed to the public? Is there a CVE list somewhere that I can browse?

  • unitedwithme@lemmy.today
    link
    fedilink
    English
    arrow-up
    5
    ·
    5 hours ago

    Just open source the code, that’s the best way to help validate the systems used. Though, no telling if they’d be modified, update/patched, or using a compromised fork, so who knows…