October 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-2302) Default ASYM_ENCRYPT asym_keylength is considered breakable

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/JGRP-2302?page=com.atlassian.jira.plugin.... ] Radoslav Husar moved WFLY-11192 to JGRP-2302: --------------------------------------------- Project: JGroups (was: WildFly) Key: JGRP-2302 (was: WFLY-11192) Component/s: (was: Clustering) Affects Version/s: 4.0.15 (was: 14.0.0.Final) Fix Version/s: (was: 15.0.0.Alpha1) > Default ASYM_ENCRYPT asym_keylength is considered breakable > ----------------------------------------------------------- > > Key: JGRP-2302 > URL: https://issues.jboss.org/browse/JGRP-2302 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.0.15 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > > JGroups default asym_keylength is 512, however RSA keys less than 1024 bits are considered breakable (e.g. https://www.oracle.com/technetwork/java/javase/8-compatibility-guide-2156... ) > We should baseline the default to a secure size universally supported in our supported JDKs. Also, since JDK8 the default is 2048. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2302) Default ASYM_ENCRYPT asym_keylength is considered breakable

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/JGRP-2302?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated JGRP-2302: --------------------------------- Git Pull Request: (was: https://github.com/wildfly/wildfly/pull/11739) > Default ASYM_ENCRYPT asym_keylength is considered breakable > ----------------------------------------------------------- > > Key: JGRP-2302 > URL: https://issues.jboss.org/browse/JGRP-2302 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.0.15 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > > JGroups default asym_keylength is 512, however RSA keys less than 1024 bits are considered breakable (e.g. https://www.oracle.com/technetwork/java/javase/8-compatibility-guide-2156... ) > We should baseline the default to a secure size universally supported in our supported JDKs. Also, since JDK8 the default is 2048. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11192) Default ASYM_ENCRYPT asym_keylength is considered breakable

by Radoslav Husar (Jira)

Radoslav Husar created WFLY-11192: ------------------------------------- Summary: Default ASYM_ENCRYPT asym_keylength is considered breakable Key: WFLY-11192 URL: https://issues.jboss.org/browse/WFLY-11192 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 14.0.0.Final Reporter: Radoslav Husar Assignee: Radoslav Husar Fix For: 15.0.0.Alpha1 JGroups default asym_keylength is 512, however RSA keys less than 1024 bits are considered breakable (e.g. https://www.oracle.com/technetwork/java/javase/8-compatibility-guide-2156... ) We should baseline the default to a secure size universally supported in our supported JDKs. Also, since JDK8 the default is 2048. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-458) Upgrade Clusters to OpenShift 3.11

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-458?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo reassigned SWSQE-458: --------------------------------------------- Assignee: Guilherme Baufaker Rêgo (was: Michael Foley) > Upgrade Clusters to OpenShift 3.11 > ---------------------------------- > > Key: SWSQE-458 > URL: https://issues.jboss.org/browse/SWSQE-458 > Project: Kiali QE > Issue Type: Task > Reporter: Matt Mahoney > Assignee: Guilherme Baufaker Rêgo > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-458) Upgrade Clusters to OpenShift 3.11

by Matt Mahoney (Jira)

Matt Mahoney created SWSQE-458: ---------------------------------- Summary: Upgrade Clusters to OpenShift 3.11 Key: SWSQE-458 URL: https://issues.jboss.org/browse/SWSQE-458 Project: Kiali QE Issue Type: Task Reporter: Matt Mahoney Assignee: Michael Foley -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2301) UFC: add back to configs even if TCP is transport

by Bela Ban (Jira)

Bela Ban created JGRP-2301: ------------------------------ Summary: UFC: add back to configs even if TCP is transport Key: JGRP-2301 URL: https://issues.jboss.org/browse/JGRP-2301 Project: JGroups Issue Type: Enhancement Reporter: Bela Ban Assignee: Bela Ban Fix For: 4.0.16 Currently, none of the TCP-based stacks have UFC in them. This is bad, as async messages can overwhelm the receiver. Point in case is cross-site replication: the bridge using TCP replicates updates to the other site masters quickly, but the updates are only passed to the thread pool for processing, exhausting memory over time. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11178) WSTrustTestCase failing on IBM

by Jan Blizňák (Jira)

[ https://issues.jboss.org/browse/WFLY-11178?page=com.atlassian.jira.plugin... ] Jan Blizňák commented on WFLY-11178: ------------------------------------ At the moment, I don't know how to obtain info about class init order. No, the linked picketlink code is the only place where this property is manipulated with. It is executed in both cases - IBM and OpenJDK before the attempt to call SchemaFactory.newInstance(). Is there an easy way how to list currently loaded modules, for given deployment? I am trying to prepare reduced reproducer that would show the issue too. > WSTrustTestCase failing on IBM > ------------------------------ > > Key: WFLY-11178 > URL: https://issues.jboss.org/browse/WFLY-11178 > Project: WildFly > Issue Type: Bug > Components: Web Services > Affects Versions: 14.0.0.Final > Reporter: Jan Blizňák > Assignee: Alessio Soldano > Priority: Major > Attachments: log.txt > > > As discovered during investigation in WFLY-10336, we are now getting test failures in WSTrustTestCase when IBM JDK is used. The relevant part of the exception is: > {code:java} > Caused by: java.lang.IllegalArgumentException: Provider org.apache.xerces.jaxp.validation.XMLSchemaFactory not found > at javax.xml.validation.SchemaFactory.newInstance(Unknown Source) > at org.opensaml.core.xml.config.XMLConfigurator.<init>(XMLConfigurator.java:94) > at org.apache.wss4j.common.saml.OpenSAMLBootstrap.bootstrap(OpenSAMLBootstrap.java:85) > at org.apache.wss4j.common.saml.OpenSAMLUtil.initSamlEngine(OpenSAMLUtil.java:91) > at org.apache.wss4j.common.saml.OpenSAMLUtil.initSamlEngine(OpenSAMLUtil.java:75) > at org.apache.wss4j.common.saml.SamlAssertionWrapper.<init>(SamlAssertionWrapper.java:184) > at org.apache.cxf.sts.token.provider.SAMLTokenProvider.createSamlToken(SAMLTokenProvider.java:308) > at org.apache.cxf.sts.token.provider.SAMLTokenProvider.createToken(SAMLTokenProvider.java:120) > ... 102 more > {code} > It turned out the issue is in wildfly for some time, the breaking change was identified as https://github.com/wildfly/wildfly-core/pull/3201/ -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3133) Add support for EXPECTED conditions on new object

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-3133?page=com.atlassian.jira.plugi... ] Klara Kufova updated DROOLS-3133: --------------------------------- Story Points: 5 > Add support for EXPECTED conditions on new object > ------------------------------------------------- > > Key: DROOLS-3133 > URL: https://issues.jboss.org/browse/DROOLS-3133 > Project: Drools > Issue Type: Story > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Daniele Zonca > Priority: Major > > As user I want to define in the EXPECTED section conditions on instances that are generated during rule execution and not only on object defined in the GIVEN section. > In other words I want to define I expect that during rule execution it will be generated an instance of a specific type and that satisfy some conditions -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3082) Header Edit Mode remains active

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-3082?page=com.atlassian.jira.plugi... ] Klara Kufova updated DROOLS-3082: --------------------------------- Story Points: 3 > Header Edit Mode remains active > ------------------------------- > > Key: DROOLS-3082 > URL: https://issues.jboss.org/browse/DROOLS-3082 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.13.0.Final > Reporter: Jozef Marko > Assignee: Gabriele Cardosi > Priority: Minor > Attachments: Screenshot from 2018-10-05 15-23-39.png > > > Sometimes during editing header cells they remains in edit mode unexpectedly. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3082) Header Edit Mode remains active

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-3082?page=com.atlassian.jira.plugi... ] Klara Kufova reassigned DROOLS-3082: ------------------------------------ Assignee: Gabriele Cardosi (was: Daniele Zonca) > Header Edit Mode remains active > ------------------------------- > > Key: DROOLS-3082 > URL: https://issues.jboss.org/browse/DROOLS-3082 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.13.0.Final > Reporter: Jozef Marko > Assignee: Gabriele Cardosi > Priority: Minor > Attachments: Screenshot from 2018-10-05 15-23-39.png > > > Sometimes during editing header cells they remains in edit mode unexpectedly. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 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 October 2018