I think in this text, details like the timeline are simplified a bit too much. But I agree with the general tendency described.

There was never a time where software was perfect, but the accelerating cadence of serious, widespread incidents with real-world effects seems real.

  • corsicanguppy@lemmy.ca
    link
    fedilink
    English
    arrow-up
    21
    arrow-down
    1
    ·
    edit-2
    21 hours ago

    This guy is delightfully close to a cause, but not really.

    In the enterprise space, we largely avoid NPM or Composer, et al, because those very best-practice docs (iso27002, here, later SLSA) prohibit repos that obscure or frustrate validation and code pedigree; and the gleeful incestuous inclusion of projects within projects means source code isn’t properly managed - a failure - so npm won’t do. SBoM and validation is key.

    So that covers half his premise; and while some shops or people use and love npm and cpan et al, the kind of people maintaining banking or travel systems should most absofuckinglutely NOT be using those ecosystems lest they lose their certification the first time a clued audit comes through. You wouldn’t accept code violations from your architect or your builders, and programmers are the same way in that space.

    The problem, it seems, is sloppy people doing sloppy things and not getting caught.

    I’m sure Ai is a big help with this, but it’s only enabled by the same sloppiness that was already present.

    Great news: civil courtrooms try negligence and code-violation cases all the time.

    • HaraldvonBlauzahn@feddit.orgOP
      link
      fedilink
      English
      arrow-up
      6
      ·
      14 hours ago

      In the enterprise space, we largely avoid NPM or Composer, et al, because those very best-practice docs (iso27002, here, later SLSA) prohibit repos that obscure or frustrate validation and code pedigree; and the gleeful incestuous inclusion of projects within projects means source code isn’t properly managed - a failure - so npm won’t do.

      Rust (that is, cargo and crates.io) does in principle the same, and Java (via Maven) as well. Their quality is arguably better, but a lot of modern software has hundreds of dependencies.

      I am wondering whether the SBOM philosophy is merely a box-ticking exercise. It does not buy you much when you know you have a buggy 15 years old TCP stack in your industrial control, but you can’t upgrade it because there is no storage left on your device. And the same holds for Cisco routers. Constantly upgrading works,in my experience, only with completely open systems like Linux, on open hardware.

      • HaraldvonBlauzahn@feddit.orgOP
        link
        fedilink
        English
        arrow-up
        2
        ·
        edit-2
        13 hours ago

        but a lot of modern software has hundreds of dependencies.

        Which by the way also leads to an interesting state of matter once you reach the point where every dependency problem you fix causes on average more than one new problem elsewhere. The reason is that if dependencies are not strictly backwards-compatible, that’s a breaking change – and with large depedency graphs, breaking changes tend to cause more breaking changes. You get kind of a nuclear chain reaction.

        • gian @lemmy.grys.it
          link
          fedilink
          English
          arrow-up
          2
          ·
          10 hours ago

          Which is the reason you lock down the dependencies and maybe you build a in-house server to host them (be NPM, composer of whatever) so everyone fetch a certified version and it is the same for everyone on every project, with an upgrade that need to follow a strict process.

    • solrize@lemmy.ml
      link
      fedilink
      English
      arrow-up
      9
      ·
      edit-2
      20 hours ago

      SBoM and validation is key.

      Yes, unfortunately the SBoM too often is a Yaml file that gets changed every time someone wants to use a new Ruby gem. https://openssf.org/projects/slsa/ is a page with a small blurb and an embedded video! slsa.dev looks interesting and I’ll check into it later.

      Management everywhere cares about velocity more than they care about anything else. They’ll always find workarounds for anything requiring careful thought.