I looked into this and was tempted as there is less read locking and better RNG performance but they stripped the SSL_get1_curves() API which I depend on for bot detection plus I would have to recompile nginx and all its modules everywhere so in the end it was not tempting enough for me. Perhaps I am just lazier in my older age.
>We do not fully understand the motivations that led to the public APIs and internal complexity we’ve described here. We’ve done our best to reverse engineer them by asking “what would motivate someone to do this” and often we’ve found ourselves coming up short.
Surely they thought of it but didn't say it out loud... to keep it exploitable, maybe?
No, that's not what's being implied. They're just saying they don't understand why OpenSSL has added so many indirections to otherwise straightforward operations.
Source: I am friends with the maintainers who wrote this and was one of the people who reviewed it in draft form.
tangential, but I've always wondered what the point of these random pictures of a lock, gears, or unrelated little voxel art are for? Pre-LLMs, they were often hit or miss in terms of how much they added depending on if they were a random stock image or something someone drew.
But now, with LLMs, they're more available to customize, and it seems like people aren't actually thinking anymore about why they should be there. I think I'm implicitly biasing against the rest of the content in articles which have them as a result, since it's probably a sign of some level of lack of care/thought.
I kinda wonder what if Microsoft (or any major software company) would give their engineers a few decades of time just to refactor their existing systems, opposite of piling on new features. Will it result a much cleaner code, better architect, and stable product?
The last Windows I daily use was Windows 7 Home (same era with Windows Server 2008). The newer ones don't really improved much featurely from my (user) point of view, and from what I've heard, it's getting more sloppyer every newer version.
> what if Microsoft would give their engineers a few decades of time just to refactor their existing systems
They wouldn't, even if they didn't care about shipping new features. The technical complexity inside Windows/Office/old core MS offerings arises only in small part from ordinary tech debt--that is, things fixable without changing observable behavior. The lion's share of that complexity is because of Microsoft's priority to avoid breaking compatibility (backwards, or with hardware/software combos that work) at all costs.
That means that a refactor-only decade would achieve little unless that compatibility priority were changed.
The Windows user-mode innards have been significantly refactored. Many of the core system DLLs that apps link to are just redirects to the actual implementation now. Much of the jank seems to be in the UI.
It's just as likely it would end up as an overengineered mess. And that's without considering backwards compatibility constraints, which are one of the biggest maintenance burdens.
Make you wonder what they've been testing this on. Even NetBSD doesn't have a recent release for Itanium. Crazy that you can run NetBSD 11.0 on HPPA, but not Itanium, given that HPPA is in some sense the pre-cursor to Itanium.
> Support for DTLS 1.3 (RFC 9147).
Refer to the ossl-guide-dtlsv13(7) manual page for details.
DTLS 1.3 is a huge improvement over 1.2 for efficiency and simplicity. I can’t speak to the OpenSSL implementation but it’s great that support is finally released.
Interesting they're adding new support for DTLS 1.3 when afaict most new applications are defaulting to QUIC datagram mode. I have something built around DTLS 1.3 and am using wolfssl for that reason, will have to check this out.
Context: https://cryptography.io/en/latest/statements/state-of-openss...
Surely they thought of it but didn't say it out loud... to keep it exploitable, maybe?
Source: I am friends with the maintainers who wrote this and was one of the people who reviewed it in draft form.
But now, with LLMs, they're more available to customize, and it seems like people aren't actually thinking anymore about why they should be there. I think I'm implicitly biasing against the rest of the content in articles which have them as a result, since it's probably a sign of some level of lack of care/thought.
What a throwback. afaik Windows Server 2008 R2 had Itanium updates until 2020 and paid support until this year. Pretty good run to say at least
https://github.com/openssl/openssl/blob/c69b5af10a754051274e...
“ The executable format that works on HPE Nonstop Compute's OSS is ELF64-bit, Big_Endian, X86_64. ”
https://inbox.sourceware.org/gcc-help/AM7PR02MB6483A12F6B98D...
The last Windows I daily use was Windows 7 Home (same era with Windows Server 2008). The newer ones don't really improved much featurely from my (user) point of view, and from what I've heard, it's getting more sloppyer every newer version.
They wouldn't, even if they didn't care about shipping new features. The technical complexity inside Windows/Office/old core MS offerings arises only in small part from ordinary tech debt--that is, things fixable without changing observable behavior. The lion's share of that complexity is because of Microsoft's priority to avoid breaking compatibility (backwards, or with hardware/software combos that work) at all costs.
That means that a refactor-only decade would achieve little unless that compatibility priority were changed.
DTLS 1.3 is a huge improvement over 1.2 for efficiency and simplicity. I can’t speak to the OpenSSL implementation but it’s great that support is finally released.
I've been linking a lot of stuff against boringssl during that time, I suppose...
0. https://www.libressl.org/
A sad day. End of an era *salute*
i think a project like this would slough old architecture like mad and let major versions tick, but they forge on...
(Not a strange question given the recent PHP vulns found by AI.)