I came across an NPR Article this morning discussing malware believed to have been installed by China on many small office / home routers across the United States.

National Cyber Director Harry Coker Jr. alluded to the fact that the US does the exact same thing by advising The House Select Committee on the Chinese Communist Party to “continu[e] operating with confidence, not yielding the initiative, not merely staying on the defensive, but being as strong as the United States has always been”

The vulnerability that was exploited was “outdated Cisco or NetGear devices that were no longer subject to software updates.” These vulnerabilities were present because proprietary equipment and software was no-longer being maintained. This is far less likely to have occurred with routers using FLOSS, like OpenWRT. Such routers regularly receive updates for many years after the original equipment manufacturer has stopped supporting them.

Only with FLOSS hardware, software, and shared standards can nation states have digital sovereignty, compatibility, and security. If all sides are using the same FLOSS standards, then they can host their own services without dependence on a foreign tech sector, they can maintain international compatibility, and any vulnerabilities affect all parties equally. Therefore, it is in the best interest of each party to contribute fixes which ensure their own infrastructure is secure, and simultaneously provide security & functionality to each other party.

  • GreyBeard@lemmy.one
    link
    fedilink
    arrow-up
    1
    ·
    11 months ago

    I’ve always felt that public money should require public code. It makes total sense, unless you are a politician who wants to give favors and earn kickbacks.

    • Letstakealook@lemm.ee
      link
      fedilink
      arrow-up
      0
      ·
      11 months ago

      When the government contracts for IT equipment, it comes with terms about maintenance, updates, and life cycle. It would require a much higher cost, especially in FTE funding, to ensure that open source code is viable and safe before deployment. I’m not implying that there are zero risks or errors with contracts, though they do provide some benefits.

      • ShortN0te@lemmy.ml
        link
        fedilink
        arrow-up
        1
        ·
        11 months ago

        to ensure that open source code is viable and safe before deployment.

        It takes the same amount of time to develop closed source as open source software. So doea validating and certifying it.

        Not sure why it should be more expensiv to put the moeny towards a OSS solution.