Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Compatibly of TCN 2.0.12 with Netty 4.1.25? Mutual TLS is maybe broken?
See original GitHub issueI don’t have much info about it at the moment and won’t be able to investigate it for the next two weeks but upgrading TCN (OpenSSL) from 2.0.10 to 2.0.12 seems to break something. On the first glance it’s mutual TLS but I’m not sure (i.e. could be all TLS).
I’ll be able to provide more info when I’m back.
Expected behavior
Actual behavior
Steps to reproduce
Minimal yet complete reproducer code (or URL to code)
Netty version
JVM version (e.g. java -version)
OS version (e.g. uname -a)
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Authentication
Netty -tcnative with BoringSSL includes BoringSSL statically linked in the binary. This means the system's pre-installed TLS libraries will not be used.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@normanmaurer just to close the loop, I can confirm that it was a 2.0.12 w/ 4.1.25 incompatibility.
What are your thoughts on semver’ing TCN? Would the incompatibly warranted a TCN release of 2.1.0 instead of 2.0.12?
Let me close this as stated its because its not compatible.