3 ms·
We do B2B software in banking and this is something we've been anticipating for quite some time now. We were implicated in that log4j exploit via a (very) trans
by bob1029 4y ago
We do B2B software in banking and this is something we've been anticipating for quite some time now. We were implicated in that log4j exploit via a (very) transitive, cross-language dependency.
We killed 100% of our Java usage over this. We simply don't have enough in-house talent to make sure things are safe in that bucket. Our customers thought this was a glorious plan as well.
I do think most of the pain should fall to the vendors of the end product, not their oss suppliers. If your shop doesn't have enough resources to validate all vendors are safe, maybe figure out how to do it with fewer vendors.
At a certain level, if you are selling deficient products to sensitive customers, you really need to be stopped. Anything impacting finance, PII, safety, infrastructure, defense, etc. Some extra regulations could go a long way in these areas.
- malfist 4y agoYou ditched all java over a single bug? That seems extreme..... Did you ditch ssl over heartbleed?
- richbell 4y ago> You ditched all java over a single bug? A bug in a third-party dependency, no less.
- bob1029 4y agoAt the time, Java accounted for <1% of our codebase/product, so it made sense to do so.
- javajosh 4y agoDid they ditch CPUs after spectre?
- wilsonjholmes 4y agoFinally! I can go outside! : ' )