2 ms·
I don't expect every user to audit code. But one of the audits I was privvy to was a part of the federal government and had really stringent requirements for t
by klyrs 5y ago
I don't expect every user to audit code. But one of the audits I was privvy to was a part of the federal government and had really stringent requirements for the code that they run -- which, of course, includes tracking down all the dependencies, and, yes, is expensive. The fact that this extremely widely-used project never hit such an audit is a curiosity. And a bit of a tragedy of the commons -- many millions of dollars of commerce has depended on this project, and now folks are up in arms because every individual decided that it wasn't their problem to investigate.
- jacquesm 5y agoIndeed. Every Node.js/npm installation, ever.
- TedDoesntTalk 5y agoEven with an audit and 100% unit test coverage, and static code analysis, vulnerabilities slip through. Software is not perfect and you do not have a silver bullet.
- klyrs 5y agoI'd agree if this was the first CVE. But that got some attention to log4j, which quickly exposed two more CVEs. There's no such thing as perfect, but these problems almost certainly would have been caught by a competent security audit.
- TedDoesntTalk 5y agoHas any of your software been through a security audit? Mine has. It’s 99.9% OWASP coverage with some automated fuzzing with almost no imagination applied by the auditors. You’re assigning far too much ability to auditors.
- klyrs 5y agoUpthread, I mentioned that I've been party to it three times. And yes, auditor skill and methods vary.