March 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-1535) CipherSuiteSelector does not know about CHACHA20_POLY1305

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-1535?page=com.atlassian.jira.plugin.s... ] David Lloyd commented on ELY-1535: ---------------------------------- https://tools.ietf.org/html/rfc7905 > CipherSuiteSelector does not know about CHACHA20_POLY1305 > --------------------------------------------------------- > > Key: ELY-1535 > URL: https://issues.jboss.org/browse/ELY-1535 > Project: WildFly Elytron > Issue Type: Bug > Reporter: Mike Yoder > Assignee: Darran Lofthouse > > I was trying to be a good person and implement the Mozilla "Modern" cipher suite described here: > https://wiki.mozilla.org/Security/Server_Side_TLS > I'm doing this in a keycloak server. The config line there looks like > {noformat} > <https-listener security-realm="ApplicationRealm" > enabled-protocols="SSLv2Hello,TLSv1.2" > enabled-cipher-suites="TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384:TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384:TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256:TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256:TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256:TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256:TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384:TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384:TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256:TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256" > name="default" > socket-binding="httpish" > enable-http2="true" > proxy-address-forwarding="true" > /> > {noformat} > But I got this: > {noformat} > 13:20:46,574 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service org.wildfly.undertow.listener.default: org.jboss.msc.service.StartException in serv > ice org.wildfly.undertow.listener.default: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1978) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > Caused by: java.lang.IllegalArgumentException: ELY05016: Unrecognized token "TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256" in mechanism selection string "TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384:TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384:TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256:TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256:TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256:TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256:TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384:TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384:TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256:TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256" > at org.wildfly.security.ssl.CipherSuiteSelector.fromString(CipherSuiteSelector.java:423) > at org.wildfly.extension.undertow.HttpsListenerService.startListening(HttpsListenerService.java:120) > at org.wildfly.extension.undertow.ListenerService.start(ListenerService.java:169) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955) > {noformat} > With a little digging it appears that CipherSuiteSelector doesn't know what CHACHA20 or POLY1305 are. See: > https://github.com/wildfly-security/wildfly-elytron/blame/master/src/main... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9947) start page in localhost:8080 has showed "wildfly 11" and wildfly is version 12

by Hoang Vu Pham (JIRA)

[ https://issues.jboss.org/browse/WFLY-9947?page=com.atlassian.jira.plugin.... ] Hoang Vu Pham updated WFLY-9947: -------------------------------- Summary: start page in localhost:8080 has showed "wildfly 11" and wildfly is version 12 (was: start page in localhost:8080 has showed "wildfly 10" and wildfly is version 12) > start page in localhost:8080 has showed "wildfly 11" and wildfly is version 12 > ------------------------------------------------------------------------------ > > Key: WFLY-9947 > URL: https://issues.jboss.org/browse/WFLY-9947 > Project: WildFly > Issue Type: Feature Request > Reporter: Hoang Vu Pham > Assignee: Jason Greene > Priority: Minor > Fix For: 12.0.0.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9947) start page in localhost:8080 has showed "wildfly 10" and wildfly is version 12

by Hoang Vu Pham (JIRA)

Hoang Vu Pham created WFLY-9947: ----------------------------------- Summary: start page in localhost:8080 has showed "wildfly 10" and wildfly is version 12 Key: WFLY-9947 URL: https://issues.jboss.org/browse/WFLY-9947 Project: WildFly Issue Type: Feature Request Reporter: Hoang Vu Pham Assignee: Jason Greene Priority: Minor Fix For: 12.0.0.Final -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-1535) CipherSuiteSelector does not know about CHACHA20_POLY1305

by Mike Yoder (JIRA)

Mike Yoder created ELY-1535: ------------------------------- Summary: CipherSuiteSelector does not know about CHACHA20_POLY1305 Key: ELY-1535 URL: https://issues.jboss.org/browse/ELY-1535 Project: WildFly Elytron Issue Type: Bug Reporter: Mike Yoder Assignee: Darran Lofthouse I was trying to be a good person and implement the Mozilla "Modern" cipher suite described here: https://wiki.mozilla.org/Security/Server_Side_TLS I'm doing this in a keycloak server. The config line there looks like {noformat} <https-listener security-realm="ApplicationRealm" enabled-protocols="SSLv2Hello,TLSv1.2" enabled-cipher-suites="TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384:TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384:TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256:TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256:TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256:TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256:TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384:TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384:TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256:TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256" name="default" socket-binding="httpish" enable-http2="true" proxy-address-forwarding="true" /> {noformat} But I got this: {noformat} 13:20:46,574 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service org.wildfly.undertow.listener.default: org.jboss.msc.service.StartException in serv ice org.wildfly.undertow.listener.default: Failed to start service at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1978) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Caused by: java.lang.IllegalArgumentException: ELY05016: Unrecognized token "TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256" in mechanism selection string "TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384:TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384:TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256:TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256:TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256:TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256:TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384:TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384:TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256:TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256" at org.wildfly.security.ssl.CipherSuiteSelector.fromString(CipherSuiteSelector.java:423) at org.wildfly.extension.undertow.HttpsListenerService.startListening(HttpsListenerService.java:120) at org.wildfly.extension.undertow.ListenerService.start(ListenerService.java:169) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955) {noformat} With a little digging it appears that CipherSuiteSelector doesn't know what CHACHA20 or POLY1305 are. See: https://github.com/wildfly-security/wildfly-elytron/blame/master/src/main... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3588) Undertow subsystem should support arbitrary options

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-3588?page=com.atlassian.jira.plugin.... ] Stuart Douglas commented on WFLY-3588: -------------------------------------- The main use case for this is for handling when new options are added to Undertow that are not in the current schema. If this happens in a CP stream then we have to add a system property to control this, if we supported dynamic options then this would not be an issue. > Undertow subsystem should support arbitrary options > --------------------------------------------------- > > Key: WFLY-3588 > URL: https://issues.jboss.org/browse/WFLY-3588 > Project: WildFly > Issue Type: Feature Request > Components: Web (Undertow) > Reporter: Stuart Douglas > Assignee: Tomaz Cerar > > At the moment all well known options are hard coded in the schema. We should also support dynamic options where the class name is specified. This will allow the use of user defined options. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3662) If an exception occurs resuming an activity the exception is lost

by Stuart Douglas (JIRA)

Stuart Douglas created WFCORE-3662: -------------------------------------- Summary: If an exception occurs resuming an activity the exception is lost Key: WFCORE-3662 URL: https://issues.jboss.org/browse/WFCORE-3662 Project: WildFly Core Issue Type: Bug Reporter: Stuart Douglas Assignee: Stuart Douglas -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9946) The JSON-B implementation module is not properly exported to deployments

by James Perkins (JIRA)

James Perkins created WFLY-9946: ----------------------------------- Summary: The JSON-B implementation module is not properly exported to deployments Key: WFLY-9946 URL: https://issues.jboss.org/browse/WFLY-9946 Project: WildFly Issue Type: Bug Components: EE Reporter: James Perkins Assignee: James Perkins The {{javax.json.binding.api}} only imports the services from the {{org.eclipse.yasson}} implementation. However the services and the implementation need to be exported as the {{ServiceLoader}} will be loaded on the deployments class loader not the {{javax.json.binding.api}} class loader. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9944) Servlet API bridge 1.0.1.Final

by Stuart Douglas (JIRA)

Stuart Douglas created WFLY-9944: ------------------------------------ Summary: Servlet API bridge 1.0.1.Final Key: WFLY-9944 URL: https://issues.jboss.org/browse/WFLY-9944 Project: WildFly Issue Type: Component Upgrade Reporter: Stuart Douglas Assignee: Jason Greene -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9945) CDI API Bridge 1.0.1.Final

by Stuart Douglas (JIRA)

Stuart Douglas created WFLY-9945: ------------------------------------ Summary: CDI API Bridge 1.0.1.Final Key: WFLY-9945 URL: https://issues.jboss.org/browse/WFLY-9945 Project: WildFly Issue Type: Component Upgrade Reporter: Stuart Douglas Assignee: Jason Greene -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-48) Service Mesh Topology's

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/SWSQE-48?page=com.atlassian.jira.plugin.s... ] Matt Mahoney updated SWSQE-48: ------------------------------ Summary: Service Mesh Topology's (was: Test Service Mesh's) > Service Mesh Topology's > ----------------------- > > Key: SWSQE-48 > URL: https://issues.jboss.org/browse/SWSQE-48 > Project: Swift Sunshine QE > Issue Type: Task > Reporter: Matt Mahoney > Assignee: viet nguyen > > "As a SWS UI developer I want to make sure that we can visualize various different network topology meshes in the service graph" > "As a SWS backend developer I want to make sure that we can generate correct JSON from various network topology meshes" > We need to be able to quickly and easily deploy a bunch of different network topography examples in various namespaces in OpenShift/K8S for testing purposes. > There are a bunch of different posible combinations of how things can be arranged and we need to be able to verify that they are render correctly in our UI and that our backend JSON is generating them correctly. > We should be able to easily just generate these different types of setups by deploying a template in a namespace. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2018