[
https://issues.jboss.org/browse/ELY-1607?page=com.atlassian.jira.plugin.s...
]
Justin Cook commented on ELY-1607:
----------------------------------
[~mchoma] Adding the cipher suites without the OpenSSL name results in a successful
outcome, should I include them without the OpenSSL name, with null for the OpenSSL name,
or not include them?
Example:
In MechanismDatabase.properties:
TLS_PSK_WITH_ARIA_128_CBC_SHA256 =
,PSK,PSK,ARIA128,SHA256,TLSv1.2,false,HIGH,false,128,128,C0,64
Running:
/subsystem=elytron/server-ssl-context=p:add(key-manager=httpsKM,cipher-suite-filter="TLS_PSK_WITH_ARIA_128_CBC_SHA256")
Results in: {"outcome" => "success"}
Revise cipher suites exposed by Elytron
---------------------------------------
Key: ELY-1607
URL:
https://issues.jboss.org/browse/ELY-1607
Project: WildFly Elytron
Issue Type: Bug
Components: SSL
Affects Versions: 1.4.0.Final
Reporter: Martin Choma
Assignee: Justin Cook
Priority: Blocker
Fix For: 1.4.1.CR1
I know there have been discussed earlier we should revise/update database and defaults
regularly.
Checking few ciphersuites from java cipher suite list [1]. I have noticed:
* Elytron is missing CHACHA20 variants introduced in rfc 7905
* missing ciphersuites from RFC 6209
* ...
Please revise content of MechanismDatabase.properties
[1]
https://docs.oracle.com/javase/10/docs/specs/security/standard-names.html...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)