[JBoss JIRA] (WFLY-13916) Elytron server-ssl-context allowed protocols
by Sonia Zaldana (Jira)
[ https://issues.redhat.com/browse/WFLY-13916?page=com.atlassian.jira.plugi... ]
Sonia Zaldana updated WFLY-13916:
---------------------------------
Description:
SSLv2Hello is used in older JDK versions for the initial handshake message where the SSL version that will be used for the rest of the handshake is negotiated.
It is not possible to add SSLv2Hello to the list of protocols in server-ssl-context due to not being a valid value:
{code:java}
[standalone@localhost:9990 /] /subsystem=elytron/server-ssl-context=my-ssl-context:list-add(name=protocols, value=SSLv2Hello, index=0)
{
"outcome" => "failed",
"failure-description" => "WFLYCTL0129: Invalid value SSLv2Hello for protocols; legal values are [\"SSLv2\", \"SSLv3\", \"TLSv1\", \"TLSv1.1\", \"TLSv1.2\", \"TLSv1.3\"]",
"rolled-back" => true
}{code}
It is possible to add SSLv2Hello to the https connector in Undertow with legacy security as per.
> Elytron server-ssl-context allowed protocols
> --------------------------------------------
>
> Key: WFLY-13916
> URL: https://issues.redhat.com/browse/WFLY-13916
> Project: WildFly
> Issue Type: Feature Request
> Reporter: Sonia Zaldana
> Assignee: Sonia Zaldana
> Priority: Major
>
> SSLv2Hello is used in older JDK versions for the initial handshake message where the SSL version that will be used for the rest of the handshake is negotiated.
> It is not possible to add SSLv2Hello to the list of protocols in server-ssl-context due to not being a valid value:
> {code:java}
> [standalone@localhost:9990 /] /subsystem=elytron/server-ssl-context=my-ssl-context:list-add(name=protocols, value=SSLv2Hello, index=0)
> {
> "outcome" => "failed",
> "failure-description" => "WFLYCTL0129: Invalid value SSLv2Hello for protocols; legal values are [\"SSLv2\", \"SSLv3\", \"TLSv1\", \"TLSv1.1\", \"TLSv1.2\", \"TLSv1.3\"]",
> "rolled-back" => true
> }{code}
>
> It is possible to add SSLv2Hello to the https connector in Undertow with legacy security as per.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[JBoss JIRA] (ELY-2024) Elytron server-ssl-context allowed protocols
by Sonia Zaldana (Jira)
[ https://issues.redhat.com/browse/ELY-2024?page=com.atlassian.jira.plugin.... ]
Sonia Zaldana updated ELY-2024:
-------------------------------
Description:
SSLv2Hello is used in older JDK versions for the initial handshake message where the SSL version that will be used for the rest of the handshake is negotiated.
It is not possible to add SSLv2Hello to the list of protocols in server-ssl-context due to not being a valid value:
{code:java}
[standalone@localhost:9990 /] /subsystem=elytron/server-ssl-context=my-ssl-context:list-add(name=protocols, value=SSLv2Hello, index=0)
{
"outcome" => "failed",
"failure-description" => "WFLYCTL0129: Invalid value SSLv2Hello for protocols; legal values are [\"SSLv2\", \"SSLv3\", \"TLSv1\", \"TLSv1.1\", \"TLSv1.2\", \"TLSv1.3\"]",
"rolled-back" => true
}{code}
It is possible to add SSLv2Hello to the https connector in Undertow with legacy security as per.
was:It is possible to add SSLv2Hello to the https connector in Undertow with legacy security as per.
> Elytron server-ssl-context allowed protocols
> --------------------------------------------
>
> Key: ELY-2024
> URL: https://issues.redhat.com/browse/ELY-2024
> Project: WildFly Elytron
> Issue Type: Feature Request
> Reporter: Sonia Zaldana
> Assignee: Sonia Zaldana
> Priority: Major
>
> SSLv2Hello is used in older JDK versions for the initial handshake message where the SSL version that will be used for the rest of the handshake is negotiated.
> It is not possible to add SSLv2Hello to the list of protocols in server-ssl-context due to not being a valid value:
> {code:java}
> [standalone@localhost:9990 /] /subsystem=elytron/server-ssl-context=my-ssl-context:list-add(name=protocols, value=SSLv2Hello, index=0)
> {
> "outcome" => "failed",
> "failure-description" => "WFLYCTL0129: Invalid value SSLv2Hello for protocols; legal values are [\"SSLv2\", \"SSLv3\", \"TLSv1\", \"TLSv1.1\", \"TLSv1.2\", \"TLSv1.3\"]",
> "rolled-back" => true
> }{code}
>
> It is possible to add SSLv2Hello to the https connector in Undertow with legacy security as per.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[JBoss JIRA] (WFCORE-5145) Elytron server-ssl-context allowed protocols
by Sonia Zaldana (Jira)
[ https://issues.redhat.com/browse/WFCORE-5145?page=com.atlassian.jira.plug... ]
Sonia Zaldana updated WFCORE-5145:
----------------------------------
Description:
SSLv2Hello is used in older JDK versions for the initial handshake message where the SSL version that will be used for the rest of the handshake is negotiated.
It is not possible to add SSLv2Hello to the list of protocols in server-ssl-context due to not being a valid value:
{code:java}
[standalone@localhost:9990 /] /subsystem=elytron/server-ssl-context=my-ssl-context:list-add(name=protocols, value=SSLv2Hello, index=0)
{
"outcome" => "failed",
"failure-description" => "WFLYCTL0129: Invalid value SSLv2Hello for protocols; legal values are [\"SSLv2\", \"SSLv3\", \"TLSv1\", \"TLSv1.1\", \"TLSv1.2\", \"TLSv1.3\"]",
"rolled-back" => true
}{code}
It is possible to add SSLv2Hello to the https connector in Undertow with legacy security as per.
> Elytron server-ssl-context allowed protocols
> --------------------------------------------
>
> Key: WFCORE-5145
> URL: https://issues.redhat.com/browse/WFCORE-5145
> Project: WildFly Core
> Issue Type: Feature Request
> Reporter: Sonia Zaldana
> Assignee: Sonia Zaldana
> Priority: Major
>
> SSLv2Hello is used in older JDK versions for the initial handshake message where the SSL version that will be used for the rest of the handshake is negotiated.
> It is not possible to add SSLv2Hello to the list of protocols in server-ssl-context due to not being a valid value:
> {code:java}
> [standalone@localhost:9990 /] /subsystem=elytron/server-ssl-context=my-ssl-context:list-add(name=protocols, value=SSLv2Hello, index=0)
> {
> "outcome" => "failed",
> "failure-description" => "WFLYCTL0129: Invalid value SSLv2Hello for protocols; legal values are [\"SSLv2\", \"SSLv3\", \"TLSv1\", \"TLSv1.1\", \"TLSv1.2\", \"TLSv1.3\"]",
> "rolled-back" => true
> }{code}
>
> It is possible to add SSLv2Hello to the https connector in Undertow with legacy security as per.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months