upvote
The bugs were always there. The fixes are coming in fast today.
reply
I see bugs being patched, and software improving. Bring em on.
reply
Those aren't mutually exclusive... it's good that these bugs are getting fixed, but each critical severity bug that gets fixed is a headache for all of us who administer servers.
reply
I see the Kessler Syndrome play out at work.
reply
Are you implying that patching vulnerabilities will lead to more vulnerabilities? How so?
reply
Not necessarily more vulnerabilities, but I think the fear is that the continuous churn of security patches will lead to increased instability and reduced availability.

Security patch intentionally or inadvertently removes a behavior that systems X and Y depend on, so they must be fixed, and then that change cascades to dependent systems A, B, C, and D. And some of those changes will be incorrect and introduce new vulnerabilities and the cycle of life continues..

reply
You're seeing bugs get band-aided. Clanker-generated band-aids for clanker-surfaced issues aren't necessarily a proper fix, and may even be a step backwards if they introduce new issues.
reply
this bug was introduced by clankers most likely...
reply
likely based on what
reply
- version 4 got released this year

- mid 2025 a lot of people appeared contributing out of nowhere

- https://github.com/openssl/openssl/pull/29178 this rewrote the code for base64 - you can delve into it to check if this was human generated.

reply
That contributor is definitely a vibe coder these days; just look at their profile's readme: https://github.com/Nick-Nuon, the only place I have ever seen that emoji list style where every bullet point starts with an emoji is from chat bots, but chat bots really really like it.

I don't see any obvious tells from the code diff though, I would've expected chatbot code to be more commented and nothing immediately stands out.

The commit messages and PR description don't read at AI-generated at all, there are small typos and grammatical issues. For example, the sentence "Originally, the OpenSSL base64 encoding kernel includes a buffer of ctx->length" confuses word tense a bit, correct grammar would've said "Originally, the OpenSSL base64 encoding kernel included ...". Chat bots are terrible at writing but typically impeccable when it comes to word tense and spelling.

reply
Good to see that I'm not alone in seeing very weird things there - I also don't think it was vibecoded (back then, Claude wasn't there yet...) but they surely used an LLM (the passage you mentioned likely can easily be produced by pointing the LLM at 2 folders... - also scripts outputting emojis are a tell imo...).

I guess the PR back then was a bit of a CV-padding action, where they integrated their research into a widely used OSS-project. That the project maintainers just accepted this in good faith (tbh the PR is better than the last vibecoder I saw pushing into a rust-numerics projects: "enable AVX only on AMD because my broken 10 y.o. Intel clocks down when executing AVX...") bodes ill that our shared infrastructure survives this in usable "shape".

reply
This will lead to LLMs being embedded 24/7 into critical infrastructure. A "living" firewall and sysadmin.
reply
Already happening. My org has shifted agentic vuln triage/patching to p0.
reply
We could it call it a Blackwall
reply
deleted
reply
The solution is {Open,Net}BSD
reply
No it isn't.
reply
From OpenBSD, LibreSSL might be.
reply
Until enterprise distros switch or companies are convinced to switch distros, OpenSSL will remain the default. Neither seems likely to me. Even if they switched to LibreSSL, it still has vulnerabilities.
reply
Don't tell me. I work for a bank and we have automated vuln checks on our code and dependencies and we can't release in pre-prod if we don't fix the cves. Basically since last year is 1 day you deploy new code and 2 days you deploy cve fixes.
reply
That's a great process for a bank!
reply
The problem with "must fix CVEs" is that it's stupid, as most CVEs will never be a problem unless somebody alredy broke into your server. Yes, yes, security comes in layers, but the security circus is also a reality.
reply
It's also a denial of service attack on your brain because you have to do the work to prove to some beurocrat that the vulnerability can't be exploited in your environment. It usually turns out to be easier to just take the fix. And then of course we get the production downtime events because the fixed versions have other new bugs.
reply