Post
Remote status
Replies
10
@feld I don't think I've met anyone who's gotten GnuTLS to work.
@feld owned by ARM? Can I ask where that quote came from? It would be easier for me if we were, my nearest office would be an hour away rather than another continent.
@feld ah! Makes sense, thanks! 🙂
As for the core issue, there is a patch to fix that. I can get it into the codebase sooner rather than later if you still need it.
I've thought about automating the Lasted Updated timestamp to be based on the file last modified timestamp, but I can see so many ways that would go wrong
How many people are sticking WolfSSL in devices where they'll never update for years? That's what's incredibly concerning.
I'm also completely at a loss for why when even compiling with the middlebox compat mode it *still* couldn't complete the handshake. Something just seems extra broken about it.
@feld I can speculate as to why things are how they are now, but we are a large engineering team and I don't have all the history of that feature to hand. I don't typically work on the TLS side of things myself.
It is past my end of day today, but it is on my list to get that pushed forward tomorrow.
(Claude did lead me down a wrong rabbithole first, but I caught that mistake pretty quick)
I was honestly expecting to be wrong and that the root cause was a broken client implementation on the Erlang side, but something in my gut said "it worked with OpenSSL, and we know OpenSSL is a trash fire, but Occam's Razor says the drop-in replacement of WolfSSL was the only variable that changed..." and I guess it was right.