[JBoss JIRA] (WFLY-13897) infinispan-server instances provisioned by testsuite never shutdown
by Radoslav Husar (Jira)
[ https://issues.redhat.com/browse/WFLY-13897?page=com.atlassian.jira.plugi... ]
Radoslav Husar edited comment on WFLY-13897 at 9/29/20 4:25 PM:
----------------------------------------------------------------
There seem to be couple of problems at play here:
1. The graceful shutdown doesn't work because the client doesn't authenticate, because there is no such configuration - Jira TBA.
2. When graceful shutdown doesn't success, PID is not obtained on JDK8 – fix ISPN-12366.
3. When PID is obtained on JDK11, the kill command is incorrect - fix ISPN-12368.
4. If that is fixed - the kill command only kills the parent process (sh) and not the child process (java = the server) - fix ISPN-12368
was (Author: rhusar):
There seem to be couple of problems at play here:
1. The graceful shutdown doesn't work because the client doesn't authenticate, because there is no such configuration - Jira TBA.
2. When graceful shutdown doesn't success, PID is not obtained on JDK8 – also caused by ISPN-12366.
3. When PID is obtained on JDK11, the kill command is incorrect.
4. If that is fixed - the kill command only kills the parent process (sh) and not the child process (java = the server).
> infinispan-server instances provisioned by testsuite never shutdown
> -------------------------------------------------------------------
>
> Key: WFLY-13897
> URL: https://issues.redhat.com/browse/WFLY-13897
> Project: WildFly
> Issue Type: Bug
> Components: Clustering, Test Suite
> Affects Versions: 21.0.0.Beta1
> Reporter: Paul Ferraro
> Assignee: Radoslav Husar
> Priority: Critical
>
> Running the clustering testsuite locally leaves 9 instances of infinispan-server running. This wreaks havoc on the CI, which will remain running until the VM shuts down.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
3 years, 6 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:
When JBoss EAP 7.2.7 is connecting to a third party client that is running on JDK 6 the following exception is logged:
{code:java}
javax.net.ssl.SSLHandshakeException: SSLv2Hello is disabled{code}
As I understand, 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}
According to the undertow read-resource-description below, when server-ssl-context is configured in the Elytron subsystem, protocols must be defined in the server-ssl-context and not in the https connector in Undertow ("Where an SSLContext is references it should be configured with the supported protocols."):
{code:java}
/subsystem=undertow/server=default-server/https-listener=https/:read-resource-description(inherited=false,recursive=true,access-control=none)...
"enabled-protocols" => {
"type" => STRING,
"description" => "Configures SSL protocols",
"expressions-allowed" => true,
"required" => false,
"nillable" => true,
"alternatives" => ["ssl-context"],
"min-length" => 1L,
"max-length" => 2147483647L,
"deprecated" => {
"since" => "4.0.0",
"reason" => "Where an SSLContext is references it should be configured with the supported protocols."
},
"access-type" => "read-write",
"storage" => "configuration",
"restart-required" => "all-services"
},
...{code}
It is possible to add SSLv2Hello to the https connector in Undertow with legacy security as per.
was:
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: 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
>
> When JBoss EAP 7.2.7 is connecting to a third party client that is running on JDK 6 the following exception is logged:
> {code:java}
>
> javax.net.ssl.SSLHandshakeException: SSLv2Hello is disabled{code}
> As I understand, 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}
> According to the undertow read-resource-description below, when server-ssl-context is configured in the Elytron subsystem, protocols must be defined in the server-ssl-context and not in the https connector in Undertow ("Where an SSLContext is references it should be configured with the supported protocols."):
> {code:java}
> /subsystem=undertow/server=default-server/https-listener=https/:read-resource-description(inherited=false,recursive=true,access-control=none)...
> "enabled-protocols" => {
> "type" => STRING,
> "description" => "Configures SSL protocols",
> "expressions-allowed" => true,
> "required" => false,
> "nillable" => true,
> "alternatives" => ["ssl-context"],
> "min-length" => 1L,
> "max-length" => 2147483647L,
> "deprecated" => {
> "since" => "4.0.0",
> "reason" => "Where an SSLContext is references it should be configured with the supported protocols."
> },
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "all-services"
> },
> ...{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)
3 years, 6 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:
When JBoss EAP 7.2.7 is connecting to a third party client that is running on JDK 6 the following exception is logged:
{code:java}
javax.net.ssl.SSLHandshakeException: SSLv2Hello is disabled{code}
As I understand, 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}
According to the undertow read-resource-description below, when server-ssl-context is configured in the Elytron subsystem, protocols must be defined in the server-ssl-context and not in the https connector in Undertow ("Where an SSLContext is references it should be configured with the supported protocols."):
{code:java}
/subsystem=undertow/server=default-server/https-listener=https/:read-resource-description(inherited=false,recursive=true,access-control=none)...
"enabled-protocols" => {
"type" => STRING,
"description" => "Configures SSL protocols",
"expressions-allowed" => true,
"required" => false,
"nillable" => true,
"alternatives" => ["ssl-context"],
"min-length" => 1L,
"max-length" => 2147483647L,
"deprecated" => {
"since" => "4.0.0",
"reason" => "Where an SSLContext is references it should be configured with the supported protocols."
},
"access-type" => "read-write",
"storage" => "configuration",
"restart-required" => "all-services"
},
...{code}
It is possible to add SSLv2Hello to the https connector in Undertow with legacy security as per.
was:
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
>
> When JBoss EAP 7.2.7 is connecting to a third party client that is running on JDK 6 the following exception is logged:
> {code:java}
>
> javax.net.ssl.SSLHandshakeException: SSLv2Hello is disabled{code}
> As I understand, 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}
> According to the undertow read-resource-description below, when server-ssl-context is configured in the Elytron subsystem, protocols must be defined in the server-ssl-context and not in the https connector in Undertow ("Where an SSLContext is references it should be configured with the supported protocols."):
> {code:java}
> /subsystem=undertow/server=default-server/https-listener=https/:read-resource-description(inherited=false,recursive=true,access-control=none)...
> "enabled-protocols" => {
> "type" => STRING,
> "description" => "Configures SSL protocols",
> "expressions-allowed" => true,
> "required" => false,
> "nillable" => true,
> "alternatives" => ["ssl-context"],
> "min-length" => 1L,
> "max-length" => 2147483647L,
> "deprecated" => {
> "since" => "4.0.0",
> "reason" => "Where an SSLContext is references it should be configured with the supported protocols."
> },
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "all-services"
> },
> ...{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)
3 years, 6 months
[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:
When JBoss EAP 7.2.7 is connecting to a third party client that is running on JDK 6 the following exception is logged:
{code:java}
javax.net.ssl.SSLHandshakeException: SSLv2Hello is disabled{code}
As I understand, 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}
According to the undertow read-resource-description below, when server-ssl-context is configured in the Elytron subsystem, protocols must be defined in the server-ssl-context and not in the https connector in Undertow ("Where an SSLContext is references it should be configured with the supported protocols."):
{code:java}
/subsystem=undertow/server=default-server/https-listener=https/:read-resource-description(inherited=false,recursive=true,access-control=none)...
"enabled-protocols" => {
"type" => STRING,
"description" => "Configures SSL protocols",
"expressions-allowed" => true,
"required" => false,
"nillable" => true,
"alternatives" => ["ssl-context"],
"min-length" => 1L,
"max-length" => 2147483647L,
"deprecated" => {
"since" => "4.0.0",
"reason" => "Where an SSLContext is references it should be configured with the supported protocols."
},
"access-type" => "read-write",
"storage" => "configuration",
"restart-required" => "all-services"
},
...{code}
It is possible to add SSLv2Hello to the https connector in Undertow with legacy security as per.
was:
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
>
> When JBoss EAP 7.2.7 is connecting to a third party client that is running on JDK 6 the following exception is logged:
> {code:java}
>
> javax.net.ssl.SSLHandshakeException: SSLv2Hello is disabled{code}
> As I understand, 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}
> According to the undertow read-resource-description below, when server-ssl-context is configured in the Elytron subsystem, protocols must be defined in the server-ssl-context and not in the https connector in Undertow ("Where an SSLContext is references it should be configured with the supported protocols."):
> {code:java}
> /subsystem=undertow/server=default-server/https-listener=https/:read-resource-description(inherited=false,recursive=true,access-control=none)...
> "enabled-protocols" => {
> "type" => STRING,
> "description" => "Configures SSL protocols",
> "expressions-allowed" => true,
> "required" => false,
> "nillable" => true,
> "alternatives" => ["ssl-context"],
> "min-length" => 1L,
> "max-length" => 2147483647L,
> "deprecated" => {
> "since" => "4.0.0",
> "reason" => "Where an SSLContext is references it should be configured with the supported protocols."
> },
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "all-services"
> },
> ...{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)
3 years, 6 months
[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)
3 years, 6 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)
3 years, 6 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)
3 years, 6 months