July 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-611) Unintentional integer overflow in LongNameSetPermissionCollection

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-611?page=com.atlassian.jira.plugin.sy... ] David Lloyd resolved ELY-611. ----------------------------- Resolution: Done > Unintentional integer overflow in LongNameSetPermissionCollection > ----------------------------------------------------------------- > > Key: ELY-611 > URL: https://issues.jboss.org/browse/ELY-611 > Project: WildFly Elytron > Issue Type: Bug > Affects Versions: 1.1.0.Beta7 > Reporter: Ondrej Lukas > Assignee: David Lloyd > Labels: static_analysis > Fix For: 1.1.0.Beta8 > > > There are potentially overflowing expressions in org.wildfly.security.permission.LongNameSetPermissionCollection in {{getBitsForName}} method. Expressions {{1 << nameEnumeration.size()}} and {{1 << nameEnumeration.indexOf(name)}} are evaluated as integer but assigned to {{bits}} variable which is long. It can be avoided by casting {{1}} to long. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-614) Missing null check in equals() method of AbstractPermission

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-614?page=com.atlassian.jira.plugin.sy... ] David Lloyd resolved ELY-614. ----------------------------- Resolution: Done > Missing null check in equals() method of AbstractPermission > ----------------------------------------------------------- > > Key: ELY-614 > URL: https://issues.jboss.org/browse/ELY-614 > Project: WildFly Elytron > Issue Type: Bug > Affects Versions: 1.1.0.Beta7 > Reporter: Ondrej Lukas > Assignee: David Lloyd > Labels: static_analysis > Fix For: 1.1.0.Beta8 > > > There is missing null check in {{org.wildfly.security.permission.AbstractPermission.equals(Object obj)}} method. NPE is thrown for null {{obj}} parameter. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6896) Upgrade HAL to 2.8.27.Final

by Harald Pehl (JIRA)

[ https://issues.jboss.org/browse/WFLY-6896?page=com.atlassian.jira.plugin.... ] Harald Pehl updated WFLY-6896: ------------------------------ Fix Version/s: 11.0.0.Alpha1 > Upgrade HAL to 2.8.27.Final > --------------------------- > > Key: WFLY-6896 > URL: https://issues.jboss.org/browse/WFLY-6896 > Project: WildFly > Issue Type: Component Upgrade > Components: Web Console > Reporter: Harald Pehl > Assignee: Harald Pehl > Priority: Blocker > Fix For: 10.1.0.CR1, 11.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-616) Release WildFly Elytron 1.0.3.Final

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-616: ------------------------------------ Summary: Release WildFly Elytron 1.0.3.Final Key: ELY-616 URL: https://issues.jboss.org/browse/ELY-616 Project: WildFly Elytron Issue Type: Release Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.0.3.CR1 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-438) There is not possibility to use alternative JSSE Cipher Suite Names for IBM JDK

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-438?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse resolved ELY-438. ---------------------------------- Resolution: Done > There is not possibility to use alternative JSSE Cipher Suite Names for IBM JDK > ------------------------------------------------------------------------------- > > Key: ELY-438 > URL: https://issues.jboss.org/browse/ELY-438 > Project: WildFly Elytron > Issue Type: Bug > Components: SSL > Reporter: Hynek Švábek > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 1.1.0.Beta8, 1.0.3.CR1 > > > There is not possibility to use alternative JSSE Cipher Suite Names for IBM JDK8 > Interchange TLS prefix to SSL and vice versa is not supported. > Here is list of standard JSSE Cipher Suite Names > http://docs.oracle.com/javase/8/docs/technotes/guides/security/StandardNa... > In my opinion this file is mapping file for our purpose. It is? > https://github.com/wildfly-security/wildfly-elytron/blob/master/src/main/... > For IBM JDK are different JSSE Cipher Suite Names (different prefix). > Most items from this list are missing in MechanismDatabase.properties mentioned above. > http://www.ibm.com/support/knowledgecenter/SSYKE2_8.0.0/com.ibm.java.secu... > For example: > JSSE Cipher Suite Name *SSL_ECDHE_RSA_WITH_AES_128_CBC_SHA* is only defined for IBM JDK. > It is *TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA* for Oracle JDK. > If I try start server with JSSE Cipher Suite Name *SSL_ECDHE_RSA_WITH_AES_128_CBC_SHA* I will get this error: > {code} > 16:55:25,594 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.undertow.listener.https: org.jboss.msc.service.StartException in service jboss.undertow.listener.https: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1153) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) > at java.lang.Thread.run(Thread.java:785) > Caused by: java.lang.IllegalArgumentException: ELY05017: Token "SSL_ECDHE_RSA_WITH_AES_128_CBC_SHA" not allowed at offset 33 of mechanism selection string "SSL_ECDHE_RSA_WITH_AES_128_CBC_SHA" > at org.wildfly.security.ssl.CipherSuiteSelector.fromString(CipherSuiteSelector.java:399) > at org.wildfly.extension.undertow.HttpsListenerService.startListening(HttpsListenerService.java:125) > at org.wildfly.extension.undertow.ListenerService.start(ListenerService.java:138) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) > ... 3 more > 16:55:25,598 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([ > ("subsystem" => "undertow"), > ("server" => "default-server"), > ("https-listener" => "https") > ]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.undertow.listener.https" => "org.jboss.msc.service.StartException in service jboss.undertow.listener.https: Failed to start service > Caused by: java.lang.IllegalArgumentException: ELY05017: Token \"SSL_ECDHE_RSA_WITH_AES_128_CBC_SHA\" not allowed at offset 33 of mechanism selection string \"SSL_ECDHE_RSA_WITH_AES_128_CBC_SHA\""}} > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1680) Tab completion for echo-dmr command is broken

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1680?page=com.atlassian.jira.plugi... ] Jean-Francois Denise reassigned WFCORE-1680: -------------------------------------------- Assignee: Jean-Francois Denise (was: Alexey Loubyansky) > Tab completion for echo-dmr command is broken > --------------------------------------------- > > Key: WFCORE-1680 > URL: https://issues.jboss.org/browse/WFCORE-1680 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: Petr Kremensky > Assignee: Jean-Francois Denise > > Tab completion for echo-dmr command doesn't work. > To reproduce, start the standalone server and connect with CLI > *actual 3.0.0.Alpha5-SNAPSHOT 77673c5* > {noformat} > [standalone@localhost:9990 /] echo-dmr /sub[TAB] > core-service deployment deployment-overlay extension interface path socket-binding-group subsystem system-property > [standalone@localhost:9990 /] echo-dmr /subsystem=log[TAB] > core-service deployment deployment-overlay extension interface path socket-binding-group subsystem system-property > {noformat} > *expected* > {noformat} > [standalone@localhost:9990 /] echo-dmr /sub[TAB] > [standalone@localhost:9990 /] echo-dmr /subsystem= > [standalone@localhost:9990 /] echo-dmr /subsystem=log[TAB] > [standalone@localhost:9990 /] echo-dmr /subsystem=logging > {noformat} > The issue is not reproducible with 2.2.0.CR7 (EAP 7.1.0.DR1). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1677) Make AbstractSubsystemBaseTest#testSchemaOfSubsystemTemplates cope with substitutions properly

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1677?page=com.atlassian.jira.plugi... ] Radoslav Husar commented on WFCORE-1677: ---------------------------------------- Right, what we need to validate is the generated configs, not the template (I mean, the template could be validated too, but it would have to be different then removing the replacements and checking against the XSD). Since we do have such test, maybe this can just go away as I can't see any value being added. > Make AbstractSubsystemBaseTest#testSchemaOfSubsystemTemplates cope with substitutions properly > ---------------------------------------------------------------------------------------------- > > Key: WFCORE-1677 > URL: https://issues.jboss.org/browse/WFCORE-1677 > Project: WildFly Core > Issue Type: Feature Request > Components: Test Suite > Affects Versions: 2.2.0.CR8 > Reporter: Radoslav Husar > Assignee: Kabir Khan > Priority: Minor > > It sounds to me that the test should really be validating the generated XML files, rather than the templates. > {noformat} > testSchemaOfSubsystemTemplates[8](org.jboss.as.clustering.infinispan.subsystem.SubsystemParsingTestCase) Time elapsed: 0.052 sec <<< FAILURE! > java.lang.AssertionError: error: cvc-complex-type.2.4.b: The content of element 'subsystem' is not complete. One of '{"urn:jboss:domain:infinispan:4.0":cache-container}' is expected. > at org.junit.Assert.fail(Assert.java:88) > at org.jboss.as.subsystem.test.SchemaValidator$1.error(SchemaValidator.java:73) > at org.apache.xerces.util.ErrorHandlerWrapper.error(ErrorHandlerWrapper.java:135) > at org.apache.xerces.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:394) > at org.apache.xerces.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:325) > at org.apache.xerces.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:282) > at org.apache.xerces.impl.xs.XMLSchemaValidator$XSIErrorReporter.reportError(XMLSchemaValidator.java:481) > at org.apache.xerces.impl.xs.XMLSchemaValidator.reportSchemaError(XMLSchemaValidator.java:3571) > at org.apache.xerces.impl.xs.XMLSchemaValidator.elementLocallyValidComplexType(XMLSchemaValidator.java:3508) > at org.apache.xerces.impl.xs.XMLSchemaValidator.elementLocallyValidType(XMLSchemaValidator.java:3434) > at org.apache.xerces.impl.xs.XMLSchemaValidator.processElementContent(XMLSchemaValidator.java:3336) > at org.apache.xerces.impl.xs.XMLSchemaValidator.handleEndElement(XMLSchemaValidator.java:2383) > at org.apache.xerces.impl.xs.XMLSchemaValidator.endElement(XMLSchemaValidator.java:894) > at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(XMLNSDocumentScannerImpl.java:673) > at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1645) > at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:324) > at org.apache.xerces.parsers.XML11Configuration.parse(XML11Configuration.java:875) > at org.apache.xerces.parsers.XML11Configuration.parse(XML11Configuration.java:798) > at org.apache.xerces.jaxp.validation.StreamValidatorHelper.validate(StreamValidatorHelper.java:186) > at org.apache.xerces.jaxp.validation.ValidatorImpl.validate(ValidatorImpl.java:129) > at javax.xml.validation.Validator.validate(Validator.java:124) > at org.jboss.as.subsystem.test.SchemaValidator.validateXML(SchemaValidator.java:123) > at org.jboss.as.subsystem.test.SchemaValidator.validateXML(SchemaValidator.java:101) > at org.jboss.as.subsystem.test.AbstractSubsystemBaseTest.testSchemaOfSubsystemTemplates(AbstractSubsystemBaseTest.java:144) > at org.jboss.as.clustering.infinispan.subsystem.SubsystemParsingTestCase.testSchemaOfSubsystemTemplates(SubsystemParsingTestCase.java:130) > Results : > Failed tests: > SubsystemParsingTestCase.testSchemaOfSubsystemTemplates:130->AbstractSubsystemBaseTest.testSchemaOfSubsystemTemplates:144 error: cvc-complex-type.2.4.b: The content of element 'subsystem' is not complete. One of '{"urn:jboss:domain:infinispan:4.0":cache-container}' is expected. > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6896) Upgrade HAL to 2.8.27.Final

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-6896?page=com.atlassian.jira.plugin.... ] Brian Stansberry commented on WFLY-6896: ---------------------------------------- For this to be in 10.1 you'll need PRs against both 10.x and master. > Upgrade HAL to 2.8.27.Final > --------------------------- > > Key: WFLY-6896 > URL: https://issues.jboss.org/browse/WFLY-6896 > Project: WildFly > Issue Type: Component Upgrade > Components: Web Console > Reporter: Harald Pehl > Assignee: Harald Pehl > Priority: Blocker > Fix For: 10.1.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1681) Upgrade to WildFly Elytron 1.0.3.Final

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFCORE-1681: ---------------------------------------- Summary: Upgrade to WildFly Elytron 1.0.3.Final Key: WFCORE-1681 URL: https://issues.jboss.org/browse/WFCORE-1681 Project: WildFly Core Issue Type: Component Upgrade Components: Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 3.0.0.Alpha5 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6896) Upgrade HAL to 2.8.27.Final

by Harald Pehl (JIRA)

[ https://issues.jboss.org/browse/WFLY-6896?page=com.atlassian.jira.plugin.... ] Harald Pehl updated WFLY-6896: ------------------------------ Git Pull Request: (was: https://github.com/wildfly/wildfly/pull/8907) > Upgrade HAL to 2.8.27.Final > --------------------------- > > Key: WFLY-6896 > URL: https://issues.jboss.org/browse/WFLY-6896 > Project: WildFly > Issue Type: Component Upgrade > Components: Web Console > Reporter: Harald Pehl > Assignee: Harald Pehl > Priority: Blocker > Fix For: 10.1.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 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 July 2016