March 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SECURITY-805) Overload SecurityVaultFactory.get() to be able to specify the classloader

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/SECURITY-805?page=com.atlassian.jira.plug... ] Kabir Khan updated SECURITY-805: -------------------------------- Attachment: (was: SECURITY-805-2.diff) > Overload SecurityVaultFactory.get() to be able to specify the classloader > ------------------------------------------------------------------------- > > Key: SECURITY-805 > URL: https://issues.jboss.org/browse/SECURITY-805 > Project: PicketBox > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Kabir Khan > Assignee: Kabir Khan > Attachments: SECURITY-805-2.diff, SECURITY-805.diff > > > To work better with modular class loading in WF -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3007) Ipv6 addresses may not be canonized properly

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3007?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3007: ----------------------------------------------- Pavel Jelinek <pjelinek(a)redhat.com> changed the Status of [bug 1067348|https://bugzilla.redhat.com/show_bug.cgi?id=1067348] from ASSIGNED to ON_QA > Ipv6 addresses may not be canonized properly > -------------------------------------------- > > Key: WFLY-3007 > URL: https://issues.jboss.org/browse/WFLY-3007 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 8.0.0.Final > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > > On an ipv6 environment we may obtain IP addresses that are not properly canonized which may lead to strange issue with http proxies since the JDK ProxySelector relies on char per char matching. > All call to InetAddress.getHostName() may produce such an uncanonized address. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-805) Overload SecurityVaultFactory.get() to be able to specify the classloader

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/SECURITY-805?page=com.atlassian.jira.plug... ] Kabir Khan updated SECURITY-805: -------------------------------- Attachment: SECURITY-805-2.diff > Overload SecurityVaultFactory.get() to be able to specify the classloader > ------------------------------------------------------------------------- > > Key: SECURITY-805 > URL: https://issues.jboss.org/browse/SECURITY-805 > Project: PicketBox > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Kabir Khan > Assignee: Kabir Khan > Attachments: SECURITY-805-2.diff, SECURITY-805.diff > > > To work better with modular class loading in WF -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-805) Overload SecurityVaultFactory.get() to be able to specify the classloader

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/SECURITY-805?page=com.atlassian.jira.plug... ] Kabir Khan updated SECURITY-805: -------------------------------- Attachment: (was: SECURITY-805-2.diff) > Overload SecurityVaultFactory.get() to be able to specify the classloader > ------------------------------------------------------------------------- > > Key: SECURITY-805 > URL: https://issues.jboss.org/browse/SECURITY-805 > Project: PicketBox > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Kabir Khan > Assignee: Kabir Khan > Attachments: SECURITY-805.diff > > > To work better with modular class loading in WF -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-805) Overload SecurityVaultFactory.get() to be able to specify the classloader

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/SECURITY-805?page=com.atlassian.jira.plug... ] Kabir Khan updated SECURITY-805: -------------------------------- Attachment: SECURITY-805-2.diff > Overload SecurityVaultFactory.get() to be able to specify the classloader > ------------------------------------------------------------------------- > > Key: SECURITY-805 > URL: https://issues.jboss.org/browse/SECURITY-805 > Project: PicketBox > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Kabir Khan > Assignee: Kabir Khan > Attachments: SECURITY-805-2.diff, SECURITY-805.diff > > > To work better with modular class loading in WF -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3007) Ipv6 addresses may not be canonized properly

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3007?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3007: ----------------------------------------------- Pavel Jelinek <pjelinek(a)redhat.com> changed the Status of [bug 1067348|https://bugzilla.redhat.com/show_bug.cgi?id=1067348] from ON_QA to ASSIGNED > Ipv6 addresses may not be canonized properly > -------------------------------------------- > > Key: WFLY-3007 > URL: https://issues.jboss.org/browse/WFLY-3007 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 8.0.0.Final > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > > On an ipv6 environment we may obtain IP addresses that are not properly canonized which may lead to strange issue with http proxies since the JDK ProxySelector relies on char per char matching. > All call to InetAddress.getHostName() may produce such an uncanonized address. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3119) Management console did not show the file path correct if an expression is used

by Wolf-Dieter Fink (JIRA)

Wolf-Dieter Fink created WFLY-3119: -------------------------------------- Summary: Management console did not show the file path correct if an expression is used Key: WFLY-3119 URL: https://issues.jboss.org/browse/WFLY-3119 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Components: Domain Management, Web Console Affects Versions: 8.0.0.Final Reporter: Wolf-Dieter Fink Assignee: Brian Stansberry If the <file path=> attribute of a file-handler contains an expression the management console show this as "undifined". Change the attribute is possible anyhow an expression is used. The CLI show the correct expression: [standalone@localhost:9990 /] /subsystem=logging/periodic-rotating-file-handler=FILE:read-resource { "outcome" => "success", "result" => { "append" => true, "autoflush" => true, "enabled" => true, "encoding" => undefined, "file" => { "relative-to" => "jboss.server.log.dir", "path" => expression "${jboss.server.name}" }, "filter" => undefined, "filter-spec" => undefined, "formatter" => "%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n", "level" => "ALL", "name" => "FILE", "named-formatter" => "PATTERN", "suffix" => ".yyyy-MM-dd" } } -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1904) Usage of vault for system-properties throws java.lang.SecurityException

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1904?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-1904: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=901275, https://bugzilla.redhat.com/show_bug.cgi?id=1076507 (was: https://bugzilla.redhat.com/show_bug.cgi?id=901275) > Usage of vault for system-properties throws java.lang.SecurityException > ----------------------------------------------------------------------- > > Key: WFLY-1904 > URL: https://issues.jboss.org/browse/WFLY-1904 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Security > Affects Versions: 8.0.0.Beta1 > Reporter: Navin Surtani > Assignee: Brian Stansberry > Fix For: 8.0.1.Final > > > Steps to Reproduce: 1. add the lines in standalone.xml:- > {code} > <system-properties> > <property name="javax.net.ssl.trustStore" value="/dir/truststore.jks"/> > <property name="javax.net.ssl.trustStorePassword" value="${VAULT::blk::attr::MTBlYWUzNDEtMjI2MC00NWYzLWFiZmUtM2EyYjZkNDgyZWM4TElORV9CUkVBS215YWxpYXM=}" /> > </system-properties> > <vault> > <vault-option name="KEYSTORE_URL" value="/opt/jboss-eap-6.0/standalone/configuration/vault.jks"/> > <vault-option name="KEYSTORE_PASSWORD" value="MASK-2gTQPnrWJaqrh0pURMKAOw"/> > <vault-option name="KEYSTORE_ALIAS" value="myalias"/> > <vault-option name="SALT" value="12345678"/> > <vault-option name="ITERATION_COUNT" value="44"/> > <vault-option name="ENC_FILE_DIR" value="/opt/jboss-eap-6.0/standalone/configuration/"/> > </vault> > {code} > 2. start EAP6 in standalone mode > project_key: JBPAPP6 > Usage of vault for system-properties throws java.lang.SecurityException. > boot.log:- > {code} > 20:35:30,267 ERROR [org.jboss.as.controller.management-operation] JBAS014612: Operation ("add") failed - address: ([("system-property" => "javax.net.ssl.trustStorePassword")]): java.lang.SecurityException: JBAS013322: Vault is not initialized > at org.jboss.as.security.vault.RuntimeVaultReader.retrieveFromVault(RuntimeVaultReader.java:98) [jboss-as-security-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] > at org.jboss.as.server.RuntimeExpressionResolver.resolvePluggableExpression(RuntimeExpressionResolver.java:45) [jboss-as-server-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] > at org.jboss.as.controller.ExpressionResolverImpl.resolveExpressionsRecursively(ExpressionResolverImpl.java:58) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] > at org.jboss.as.controller.ExpressionResolverImpl.resolveExpressions(ExpressionResolverImpl.java:40) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] > at org.jboss.as.controller.ModelControllerImpl.resolveExpressions(ModelControllerImpl.java:455) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] > at org.jboss.as.controller.OperationContextImpl.resolveExpressions(OperationContextImpl.java:689) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] > at org.jboss.as.controller.operations.common.SystemPropertyAddHandler.execute(SystemPropertyAddHandler.java:112) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:397) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] > at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:284) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] > at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:211) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] > at org.jboss.as.controller.ModelControllerImpl.boot(ModelControllerImpl.java:175) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] > at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:191) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] > at org.jboss.as.server.ServerService.boot(ServerService.java:295) [jboss-as-server-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] > at org.jboss.as.server.ServerService.boot(ServerService.java:270) [jboss-as-server-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] > at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:156) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_37] > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3112) One can't change history and decay with DynamicLoadBalanceFactorProvider

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3112?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3112: ----------------------------------------------- Radoslav Husar <rhusar(a)redhat.com> changed the Status of [bug 1075215|https://bugzilla.redhat.com/show_bug.cgi?id=1075215] from ASSIGNED to POST > One can't change history and decay with DynamicLoadBalanceFactorProvider > ------------------------------------------------------------------------ > > Key: WFLY-3112 > URL: https://issues.jboss.org/browse/WFLY-3112 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Clustering > Affects Versions: 8.0.0.Final > Reporter: Michal Babacek > Assignee: Radoslav Husar > Priority: Critical > Fix For: 8.0.1.Final > > Attachments: redacted_log > > > I'm under an ugly impression that one can't actually change {{history}} and {{decay}} attributes of *DynamicLoadBalanceFactorProvider*. > I was trying to figure out why the new test suite of CustomLoadMetric tests does not pass. In order to get load figures without history and decay manipulation, I set the following: > {code} > <subsystem xmlns="urn:jboss:domain:modcluster:1.2"> > <mod-cluster-config advertise-socket="modcluster" connector="ajp"> > <dynamic-load-provider history="0"> > <custom-load-metric class="biz.karms.modcluster.CustomLoadMetric" weight="1"> > <property name="capacity" value="1000"/> > <property name="loadfile" value="/tmp/mod_cluster-eapx/loadfileA"/> > <property name="parseexpression" value="^LOAD: ([0-9]*)$"/> > </custom-load-metric> > </dynamic-load-provider> > </mod-cluster-config> > </subsystem> > {code} > The aforementioned {{history=0}} effectively means that there is just 1 "slot" for a one historical value on which decay function should work. > If you take a look at the code in [DynamicLoadBalanceFactorProvider|https://github.com/modcluster/mod_cluste...] constructor, it is apparent > that the size of the List that later serves for storing the historical values is set sooner than the actual [setHistory(int history)|https://github.com/modcluster/mod_cluster/blob/master/core/src/m...] method is called. > The actual size of that List collection wouldn't do any harm by itself but it is being used in the aforementioned class with {{.size()}} to control cycles. > The same IMHO holds for the decay attribute. > Anyhow, I put some additional logging to the [DynamicLoadBalanceFactorProvider.java|https://github.com/modcluster/mod_c...]: > {code} > // Historical value contribute an exponentially decayed factor > for (int i = 0; i < queue.size(); ++i) { > double decay = 1 / Math.pow(decayFactor, i); > totalDecay += decay; > this.log.info("KTAG: totalLoad:"+totalLoad+", with decay:"+(totalLoad+queue.get(i).doubleValue() * decay)); > totalLoad += queue.get(i).doubleValue() * decay; > } > {code} > and > {code} > try { > // Normalize load with respect to capacity > this.recordLoad(metricLoadHistory, metric.getLoad(engine) / metric.getCapacity()); > this.log.info("KTAG metricLoadHistory:"+metricLoadHistory.toString()); > totalWeight += weight; > totalWeightedLoad += this.average(metricLoadHistory) * weight; > } catch (Exception e) { > this.log.error(e.getLocalizedMessage(), e); > } > {code} > with the following being the output: [^redacted_log]. > So, despite having {{history=0}}, which should force the system to keep just 1, the current value, {{metricLoadHistory}} grew from > {noformat} > KTAG metricLoadHistory:[0.8] > {noformat} > to > {noformat} > KTAG metricLoadHistory:[0.9, 0.9, 0.9, 0.9, 0.9, 0.9, 0.9, 0.9, 0.9, 0.8] > {noformat} > which is exactly [9|https://github.com/modcluster/mod_cluster/blob/master/core/src/main/jav...] + [1|https://github.com/modcluster/mod_cluster/blob/master/core/src/main/jav...] in size :-) > WDYT? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3112) One can't change history and decay with DynamicLoadBalanceFactorProvider

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-3112?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-3112: --------------------------------- Bugzilla Update: (was: Perform) > One can't change history and decay with DynamicLoadBalanceFactorProvider > ------------------------------------------------------------------------ > > Key: WFLY-3112 > URL: https://issues.jboss.org/browse/WFLY-3112 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Clustering > Affects Versions: 8.0.0.Final > Reporter: Michal Babacek > Assignee: Radoslav Husar > Priority: Critical > Fix For: 8.0.1.Final > > Attachments: redacted_log > > > I'm under an ugly impression that one can't actually change {{history}} and {{decay}} attributes of *DynamicLoadBalanceFactorProvider*. > I was trying to figure out why the new test suite of CustomLoadMetric tests does not pass. In order to get load figures without history and decay manipulation, I set the following: > {code} > <subsystem xmlns="urn:jboss:domain:modcluster:1.2"> > <mod-cluster-config advertise-socket="modcluster" connector="ajp"> > <dynamic-load-provider history="0"> > <custom-load-metric class="biz.karms.modcluster.CustomLoadMetric" weight="1"> > <property name="capacity" value="1000"/> > <property name="loadfile" value="/tmp/mod_cluster-eapx/loadfileA"/> > <property name="parseexpression" value="^LOAD: ([0-9]*)$"/> > </custom-load-metric> > </dynamic-load-provider> > </mod-cluster-config> > </subsystem> > {code} > The aforementioned {{history=0}} effectively means that there is just 1 "slot" for a one historical value on which decay function should work. > If you take a look at the code in [DynamicLoadBalanceFactorProvider|https://github.com/modcluster/mod_cluste...] constructor, it is apparent > that the size of the List that later serves for storing the historical values is set sooner than the actual [setHistory(int history)|https://github.com/modcluster/mod_cluster/blob/master/core/src/m...] method is called. > The actual size of that List collection wouldn't do any harm by itself but it is being used in the aforementioned class with {{.size()}} to control cycles. > The same IMHO holds for the decay attribute. > Anyhow, I put some additional logging to the [DynamicLoadBalanceFactorProvider.java|https://github.com/modcluster/mod_c...]: > {code} > // Historical value contribute an exponentially decayed factor > for (int i = 0; i < queue.size(); ++i) { > double decay = 1 / Math.pow(decayFactor, i); > totalDecay += decay; > this.log.info("KTAG: totalLoad:"+totalLoad+", with decay:"+(totalLoad+queue.get(i).doubleValue() * decay)); > totalLoad += queue.get(i).doubleValue() * decay; > } > {code} > and > {code} > try { > // Normalize load with respect to capacity > this.recordLoad(metricLoadHistory, metric.getLoad(engine) / metric.getCapacity()); > this.log.info("KTAG metricLoadHistory:"+metricLoadHistory.toString()); > totalWeight += weight; > totalWeightedLoad += this.average(metricLoadHistory) * weight; > } catch (Exception e) { > this.log.error(e.getLocalizedMessage(), e); > } > {code} > with the following being the output: [^redacted_log]. > So, despite having {{history=0}}, which should force the system to keep just 1, the current value, {{metricLoadHistory}} grew from > {noformat} > KTAG metricLoadHistory:[0.8] > {noformat} > to > {noformat} > KTAG metricLoadHistory:[0.9, 0.9, 0.9, 0.9, 0.9, 0.9, 0.9, 0.9, 0.9, 0.8] > {noformat} > which is exactly [9|https://github.com/modcluster/mod_cluster/blob/master/core/src/main/jav...] + [1|https://github.com/modcluster/mod_cluster/blob/master/core/src/main/jav...] in size :-) > WDYT? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2014