[erlang-questions] Improvements in TLS error reporting
Thu Apr 28 22:47:45 CEST 2016
Sounds interesting, but remember that not all information is desirable to
have in the logs. Sometimes the protocol will hide certain errors on
purpose. Also too extensive logging can be bad. Although as a developer I
appreciate as informative error messages as possible.
Regards Ingela Erlang/OTP team - Ericsson AB
2016-04-28 18:50 GMT+02:00 Alexey Lebedeff <binarin@REDACTED>:
> I have some ideas about making SSL error reporting more friendlier for
> operators, because currently troubleshooting can be very
> problematic. If the solution outlined at the end of the message is
> acceptable, I'll make proper PR on github.
> There are several places where SSL/TLS handshake errors are being
> converted to SSL alerts. During this process some details about errors
> are being discarded, so they will fit SSL alert protocol. But the
> problem is that the same simplified errors are then used for event
> logging - and sometimes they are completely useless.
> So several times I've had to resort to adding debug print statements
> to ssl app just to find what I've done wrong in my SSL config.
> Some examples I've observed:
> - Certificate was in wrong format, but detailed error was discarded at 
> And 'internal error' message wasn't helpful at all.
> - Certificate had wrong ext-key-usage field (there was attempt to use
> server certificate as a client one) This info was happily discarded
> at . And again, the error was logged as unhelful 'handshake
> This situation can be improved. I have a suggestion to add additional
> field to SSL alert record at  which will contain detailed error
> description which is currently being throwed out. And then use this
> description in ssl_alert:alert_txt/1 at .
> erlang-questions mailing list
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the erlang-questions