zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andor Molnar (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (ZOOKEEPER-3174) Quorum TLS - support reloading trust/key store
Date Wed, 19 Dec 2018 12:50:00 GMT

     [ https://issues.apache.org/jira/browse/ZOOKEEPER-3174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Andor Molnar resolved ZOOKEEPER-3174.
-------------------------------------
       Resolution: Fixed
    Fix Version/s: 3.5.5
                   3.6.0

Issue resolved by pull request 737
[https://github.com/apache/zookeeper/pull/737]

> Quorum TLS - support reloading trust/key store
> ----------------------------------------------
>
>                 Key: ZOOKEEPER-3174
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3174
>             Project: ZooKeeper
>          Issue Type: Improvement
>    Affects Versions: 3.6.0, 3.5.5
>            Reporter: Ilya Maykov
>            Assignee: Ilya Maykov
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 3.6.0, 3.5.5
>
>          Time Spent: 12h 40m
>  Remaining Estimate: 0h
>
> The Quorum TLS feature recently added in ZOOKEEPER-236 doesn't support reloading a
trust/key store from disk when it changes. In an environment where short-lived certificates
are used and are refreshed by some background daemon / cron job, this is a problem. Let's
support reloading a trust/key store from disk when the file on disk changes.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message