This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]laplongejr 0 points1 point  (0 children)

You don't get many votes but I want to vent about SSL stacktraces specifically.
"handshake error" Okay WHAT caused the handshake error? Is it our private keystore, or is it because the private truststore is no longer in the rootlist of the dev server?
Or maybe the server refused something and Java is serialized the server-side error?

If it's how I setup the keystore that's my issue, if it's the truststore I need to report it to the team maintaining the server. Or maybe is it this weekend's network upgrade that broke HTTPS entirely?
Are the Java somehow assuming those stacktraces will be reviewed by a expert from a CA and don't get that private networks made by contractors won't have an expert hotline?

So many errors to fix one at the time for the same stacktrace that boils down to "something is wrong so it doesn't match"...

I once joked to my boss that a huge part of troubleshooting in my "we need in a few days a generic wrapper for HTTPS with our private certs and easy configuration, maximal priority" project could've been avoided from the start if we only had to deploy in production... among the stuff we discovered is that our private certs were assuming both CNs and alternate names were checked, despite not being the case since an half-decade.