Skip to content

Use legacy OpenSSL cipher naming for Candlepin's TLS connector - #789

Closed
stejskalleos wants to merge 1 commit into
theforeman:3.y-stablefrom
stejskalleos:ls/cp50
Closed

Use legacy OpenSSL cipher naming for Candlepin's TLS connector#789
stejskalleos wants to merge 1 commit into
theforeman:3.y-stablefrom
stejskalleos:ls/cp50

Conversation

@stejskalleos

Copy link
Copy Markdown
Contributor

Candlepin 5.0's Tomcat uses the new OpenSSL FFM connector, which fails to handle the IANA-style cipher names (TLS_ECDHE_...) we were using, leaving the connector with no usable ciphers and every TLS handshake failing. Switch to the legacy OpenSSL cipher naming (ECDHE-ECDSA-AES256-GCM-SHA384, ...) to make it work.

(cherry picked from commit dfe678c)

Candlepin 5.0's Tomcat uses the new OpenSSL FFM connector, which
fails to handle the IANA-style cipher names (TLS_ECDHE_...) we were
using, leaving the connector with no usable ciphers and every TLS
handshake failing. Switch to the legacy OpenSSL cipher naming
(ECDHE-ECDSA-AES256-GCM-SHA384, ...) to make it work.

(cherry picked from commit dfe678c)

@ekohl ekohl left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd prefer to take current develop and release 3.1.0 into Foreman 5.0.

@stejskalleos

Copy link
Copy Markdown
Contributor Author

not needed anymore, 3.1.0 has been released.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants