[
https://issues.apache.org/jira/browse/OMID-305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Istvan Toth updated OMID-305:
-----------------------------
Description:
Omid is currently limited to TLS 1.2
The Cipher config code is coped from ZK via HBase, we just need to sync it to
the current ZK one.
HBase has added native OpenSSL support, which we do not necessarily need in
OMID (or at least not in this ticket).
If we don't support OpenSSL, then perhaps the best course of action is to
remove the cipher selection code, and leave it to the JVM and the standard JVM
properties.
was:
Omid is currently limited to TLS 1.2
The Cipher config code is coped from ZK via HBase, we just need to sync it to
the current OMID one.
> Support TLS 1.3
> ---------------
>
> Key: OMID-305
> URL: https://issues.apache.org/jira/browse/OMID-305
> Project: Phoenix Omid
> Issue Type: Improvement
> Reporter: Istvan Toth
> Assignee: Istvan Toth
> Priority: Major
>
> Omid is currently limited to TLS 1.2
> The Cipher config code is coped from ZK via HBase, we just need to sync it to
> the current ZK one.
> HBase has added native OpenSSL support, which we do not necessarily need in
> OMID (or at least not in this ticket).
> If we don't support OpenSSL, then perhaps the best course of action is to
> remove the cipher selection code, and leave it to the JVM and the standard
> JVM properties.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
