April 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-1051) Coverity, derefere null return value in KeyStoreCredentialStore.store

by Ilia Vassilev (JIRA)

[ https://issues.jboss.org/browse/ELY-1051?page=com.atlassian.jira.plugin.s... ] Ilia Vassilev reassigned ELY-1051: ---------------------------------- Assignee: Ilia Vassilev (was: Darran Lofthouse) > Coverity, derefere null return value in KeyStoreCredentialStore.store > --------------------------------------------------------------------- > > Key: ELY-1051 > URL: https://issues.jboss.org/browse/ELY-1051 > Project: WildFly Elytron > Issue Type: Bug > Reporter: Martin Choma > Assignee: Ilia Vassilev > Priority: Critical > > Coverity found possible null dereference as {{getEntry()}} could return null. > https://scan7.coverity.com/reports.htm#v23632/p11778/fileInstanceId=12563... > {code:java|title=KeyStoreCredentialStore.java} > void store(OutputStream outputStream) throws IOException, GeneralSecurityException { > ObjectOutputStream oos = new ObjectOutputStream(outputStream); > oos.writeInt(VERSION); > Enumeration<String> ksAliases = dataKeyStore.aliases(); > while(ksAliases.hasMoreElements()) { > String alias = ksAliases.nextElement(); > KeyStore.Entry entry = dataKeyStore.getEntry(alias, convertParameter(protectionParameter)); > if (entry instanceof KeyStore.SecretKeyEntry) { > saveSecretKey(alias, oos, (KeyStore.SecretKeyEntry)entry); > } else { > throw log.unrecognizedEntryType(entry.getClass().getCanonicalName()); > } > } > oos.flush(); > oos.close(); > } > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2616) Rename DomainOperationTransformer to avoid confusion with the mixed domain transformers

by ehsavoie Hugonnet (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2616?page=com.atlassian.jira.plugi... ] ehsavoie Hugonnet updated WFCORE-2616: -------------------------------------- Component/s: Domain Management > Rename DomainOperationTransformer to avoid confusion with the mixed domain transformers > --------------------------------------------------------------------------------------- > > Key: WFCORE-2616 > URL: https://issues.jboss.org/browse/WFCORE-2616 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Affects Versions: 3.0.0.Beta12 > Reporter: ehsavoie Hugonnet > Assignee: ehsavoie Hugonnet > > DomainOperationTransformer is an operation transformation in domain mode that is completely different from the transformers API used for mixed-domains. > Rename it as transmuter to avoid confusion. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2616) Rename DomainOperationTransformer to avoid confusion with the mixed domain transformers

by ehsavoie Hugonnet (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2616?page=com.atlassian.jira.plugi... ] ehsavoie Hugonnet updated WFCORE-2616: -------------------------------------- Priority: Minor (was: Major) > Rename DomainOperationTransformer to avoid confusion with the mixed domain transformers > --------------------------------------------------------------------------------------- > > Key: WFCORE-2616 > URL: https://issues.jboss.org/browse/WFCORE-2616 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Affects Versions: 3.0.0.Beta12 > Reporter: ehsavoie Hugonnet > Assignee: ehsavoie Hugonnet > Priority: Minor > > DomainOperationTransformer is an operation transformation in domain mode that is completely different from the transformers API used for mixed-domains. > Rename it as transmuter to avoid confusion. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2616) Rename DomainOperationTransformer to avoid confusion with the mixed domain transformers

by ehsavoie Hugonnet (JIRA)

ehsavoie Hugonnet created WFCORE-2616: ----------------------------------------- Summary: Rename DomainOperationTransformer to avoid confusion with the mixed domain transformers Key: WFCORE-2616 URL: https://issues.jboss.org/browse/WFCORE-2616 Project: WildFly Core Issue Type: Enhancement Reporter: ehsavoie Hugonnet DomainOperationTransformer is an operation transformation in domain mode that is completely different from the transformers API used for mixed-domains. Rename it as transmuter to avoid confusion. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2616) Rename DomainOperationTransformer to avoid confusion with the mixed domain transformers

by ehsavoie Hugonnet (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2616?page=com.atlassian.jira.plugi... ] ehsavoie Hugonnet updated WFCORE-2616: -------------------------------------- Affects Version/s: 3.0.0.Beta12 > Rename DomainOperationTransformer to avoid confusion with the mixed domain transformers > --------------------------------------------------------------------------------------- > > Key: WFCORE-2616 > URL: https://issues.jboss.org/browse/WFCORE-2616 > Project: WildFly Core > Issue Type: Enhancement > Affects Versions: 3.0.0.Beta12 > Reporter: ehsavoie Hugonnet > Assignee: ehsavoie Hugonnet > > DomainOperationTransformer is an operation transformation in domain mode that is completely different from the transformers API used for mixed-domains. > Rename it as transmuter to avoid confusion. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2616) Rename DomainOperationTransformer to avoid confusion with the mixed domain transformers

by ehsavoie Hugonnet (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2616?page=com.atlassian.jira.plugi... ] ehsavoie Hugonnet reassigned WFCORE-2616: ----------------------------------------- Assignee: ehsavoie Hugonnet > Rename DomainOperationTransformer to avoid confusion with the mixed domain transformers > --------------------------------------------------------------------------------------- > > Key: WFCORE-2616 > URL: https://issues.jboss.org/browse/WFCORE-2616 > Project: WildFly Core > Issue Type: Enhancement > Affects Versions: 3.0.0.Beta12 > Reporter: ehsavoie Hugonnet > Assignee: ehsavoie Hugonnet > > DomainOperationTransformer is an operation transformation in domain mode that is completely different from the transformers API used for mixed-domains. > Rename it as transmuter to avoid confusion. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8476) Upgrade Artemis 1.5.4.jbossorg-002

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-8476?page=com.atlassian.jira.plugin.... ] Jeff Mesnil updated WFLY-8476: ------------------------------ Summary: Upgrade Artemis 1.5.4.jbossorg-002 (was: Upgrade Artemis 1.5.3.jbossorg-004) > Upgrade Artemis 1.5.4.jbossorg-002 > ---------------------------------- > > Key: WFLY-8476 > URL: https://issues.jboss.org/browse/WFLY-8476 > Project: WildFly > Issue Type: Component Upgrade > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ELY-1052) For the wrapped SSLEngine and SSLSockets allow further restriction of cipher suites.

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-1052: ------------------------------------- Summary: For the wrapped SSLEngine and SSLSockets allow further restriction of cipher suites. Key: ELY-1052 URL: https://issues.jboss.org/browse/ELY-1052 Project: WildFly Elytron Issue Type: Enhancement Components: SSL Reporter: Darran Lofthouse Fix For: 2.0.0.Alpha1 We should allow further configuration where this configuration leads to a union of centrally enabled cipher suites with API specified cipher suites. i.e. an administrator can centrally define the acceptable cipher suites but utilities using the APIs can restrict this further. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2615) Attribute allow-sasl-mechanisms is ignored in Elytron Authentication Configuration

by Ondrej Lukas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2615?page=com.atlassian.jira.plugi... ] Ondrej Lukas updated WFCORE-2615: --------------------------------- Description: In case when attribute allow-sasl-mechanisms from Elytron Authentication Configuration includes some SASL mechanisms then this attribute (and mechanisms configured there) is not taken into account during choosing SASL mechanism. It means that client tries to use all of mechanisms allowed on server side even if client does not allow them. e.g. in case when server side allowed DIGEST-MD5 and JBOSS-LOCAL-USER and client side allows PLAIN, then it tries to use DIGEST-MD5 and JBOSS-LOCAL-USER mechanisms. See log from wireshark in attachments. This is log for server configured through "Steps to Reproduce". This happens also for using allow-sasl-mechanisms from wildfly config and also for programatically configured client. We request blocker since it allows to use some SASL mechanisms even if they are not allowed on client side. was: In case when attribute allow-sasl-mechanisms from Elytron Authentication Configuration includes some SASL mechanisms then this attribute (and mechanisms configured there) is not taken into account during choosing SASL mechanism. It means that client tries to use all of mechanisms allowed on server side even if client does not allow them. e.g. in case when server side allowed DIGEST-MD5 and JBOSS-LOCAL-USER and client side allows PLAIN, then it tries to use DIGEST-MD5 and JBOSS-LOCAL-USER mechanisms. See log from wireshark in attachments. This is log for server configured through "Steps to Reproduce". This happens also for using allow-sasl-mechanisms from wildfly config and also for programatically configured client. We request blocker since this issue blocks RFE EAP7-567 and EAP7-568 and it allows to use some SASL mechanisms even if they are not allowed on client side. > Attribute allow-sasl-mechanisms is ignored in Elytron Authentication Configuration > ---------------------------------------------------------------------------------- > > Key: WFCORE-2615 > URL: https://issues.jboss.org/browse/WFCORE-2615 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 3.0.0.Beta10 > Reporter: Ondrej Lukas > Assignee: Darran Lofthouse > Priority: Blocker > Attachments: dep.war, wireshark.pcapng > > > In case when attribute allow-sasl-mechanisms from Elytron Authentication Configuration includes some SASL mechanisms then this attribute (and mechanisms configured there) is not taken into account during choosing SASL mechanism. It means that client tries to use all of mechanisms allowed on server side even if client does not allow them. e.g. in case when server side allowed DIGEST-MD5 and JBOSS-LOCAL-USER and client side allows PLAIN, then it tries to use DIGEST-MD5 and JBOSS-LOCAL-USER mechanisms. > See log from wireshark in attachments. This is log for server configured through "Steps to Reproduce". > This happens also for using allow-sasl-mechanisms from wildfly config and also for programatically configured client. > We request blocker since it allows to use some SASL mechanisms even if they are not allowed on client side. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2615) Attribute allow-sasl-mechanisms is ignored in Elytron Authentication Configuration

by Ondrej Lukas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2615?page=com.atlassian.jira.plugi... ] Ondrej Lukas updated WFCORE-2615: --------------------------------- Affects Version/s: 3.0.0.Beta10 > Attribute allow-sasl-mechanisms is ignored in Elytron Authentication Configuration > ---------------------------------------------------------------------------------- > > Key: WFCORE-2615 > URL: https://issues.jboss.org/browse/WFCORE-2615 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 3.0.0.Beta10 > Reporter: Ondrej Lukas > Assignee: Darran Lofthouse > Priority: Blocker > Attachments: dep.war, wireshark.pcapng > > > In case when attribute allow-sasl-mechanisms from Elytron Authentication Configuration includes some SASL mechanisms then this attribute (and mechanisms configured there) is not taken into account during choosing SASL mechanism. It means that client tries to use all of mechanisms allowed on server side even if client does not allow them. e.g. in case when server side allowed DIGEST-MD5 and JBOSS-LOCAL-USER and client side allows PLAIN, then it tries to use DIGEST-MD5 and JBOSS-LOCAL-USER mechanisms. > See log from wireshark in attachments. This is log for server configured through "Steps to Reproduce". > This happens also for using allow-sasl-mechanisms from wildfly config and also for programatically configured client. > We request blocker since this issue blocks RFE EAP7-567 and EAP7-568 and it allows to use some SASL mechanisms even if they are not allowed on client side. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2017