geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GEODE-1792) Configuration consistency in SSL configuration
Date Thu, 18 Aug 2016 18:25:20 GMT

    [ https://issues.apache.org/jira/browse/GEODE-1792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15426952#comment-15426952
] 

ASF subversion and git services commented on GEODE-1792:
--------------------------------------------------------

Commit 6ffa65231a97ef187fdd220f273942f249a0d888 in incubator-geode's branch refs/heads/feature/GEODE-420
from [~ukohlmeyer]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=6ffa652 ]

GEODE-1792: Revert:  Changed protocols and ciphers to be comma separated
Make ssl-ciphers and ssl-protocols comma separated properties.
The legacy *-ssl-ciphers and *-ssl-protocols still use space separated.


> Configuration consistency in SSL configuration
> ----------------------------------------------
>
>                 Key: GEODE-1792
>                 URL: https://issues.apache.org/jira/browse/GEODE-1792
>             Project: Geode
>          Issue Type: Improvement
>          Components: client/server, locator
>            Reporter: Udo Kohlmeyer
>
> The current ssl configuration is inconsistent in its approach. In some cases multiple
values for a property are specified as comma delimited (ssl-enabled-components) and in other
cases they are space delimited (ssl-cipher and ssl-protocol).
> We need to pick a more consistent approach and apply to all



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message