You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "C. Scott Andreas (JIRA)" <ji...@apache.org> on 2019/08/02 02:54:00 UTC
[jira] [Updated] (CASSANDRA-14991) SSL Cert Hot Reloading should
check for sanity of the new keystore/truststore before loading it
[ https://issues.apache.org/jira/browse/CASSANDRA-14991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
C. Scott Andreas updated CASSANDRA-14991:
-----------------------------------------
Complexity: Normal
Discovered By: User Report
Bug Category: Parent values: Availability(12983)Level 1 values: Unavailable(12994)
> SSL Cert Hot Reloading should check for sanity of the new keystore/truststore before loading it
> -----------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-14991
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14991
> Project: Cassandra
> Issue Type: Bug
> Components: Feature/Encryption
> Reporter: Dinesh Joshi
> Assignee: Dinesh Joshi
> Priority: Normal
> Labels: security
> Fix For: 4.0
>
>
> SSL Cert Hot Reloading assumes that the keystore & truststore are valid. However, a corrupt store or a password mismatch can cause Cassandra to fail accepting new connections as we throw away the old {{SslContext}}. This patch will ensure that we check the sanity of the certificates during startup and during hot reloading. This should protect against bad key/trust stores. As part of this PR, I have cleaned up the code a bit.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org