[
https://issues.apache.org/jira/browse/TS-3424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14347453#comment-14347453
]
Susan Hinrichs commented on TS-3424:
------------------------------------
This error was showing up for negotiating TLS 1.1 with openssl 1.0.1e. But
Brian says that they are at openssl 1.0.1i and in any case if they are not
changing openssl version and only ats, then that is unlikely to be the issue.
It would be great if we could get a reproduction case. Or a packet capture of
a failed negotiation. Unfortunately, most of my SSL API changes were in one
big commit, so blindly backing them out will be painful.
Does it fail consistently for particular client and server pairs? Or does it
seem to be timing/load related?
> SSL error: SSL3_GET_RECORD:decryption failed or bad record mac
> --------------------------------------------------------------
>
> Key: TS-3424
> URL: https://issues.apache.org/jira/browse/TS-3424
> Project: Traffic Server
> Issue Type: Bug
> Components: Core, SSL
> Reporter: Brian Geffon
> Assignee: Brian Geffon
>
> Starting with 5.2.x we're seeing SSL_ERROR_SSL type errors in
> {{ssl_read_from_net}}, when calling OpenSSL's {{ERR_error_string_n}} we see
> the error is {{1408F119:SSL routines:SSL3_GET_RECORD:decryption failed or bad
> record mac}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
