February 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-3419) JBossWeb::ssl element in connector settings should check for vaultified strings

by Anil Saldhana (JIRA)

Anil Saldhana created AS7-3419: ---------------------------------- Summary: JBossWeb::ssl element in connector settings should check for vaultified strings Key: AS7-3419 URL: https://issues.jboss.org/browse/AS7-3419 Project: Application Server 7 Issue Type: Feature Request Components: Web Affects Versions: 7.1.0.CR1 Reporter: Anil Saldhana Assignee: Jean-Frederic Clere Fix For: 7.1.0.Final Currently, the passwords in the ssl element of the connector settings are in clear text. https://community.jboss.org/wiki/JBossAS7SecuringPasswords describes very simple ways of checking whether a string is of the vault format and invoking the vault to get the decrypted string value. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

3
13
0 / 0

[JBoss JIRA] (AS7-3441) Selection models with KeyProviders break form data binding

by Heiko Braun (JIRA)

Heiko Braun created AS7-3441: -------------------------------- Summary: Selection models with KeyProviders break form data binding Key: AS7-3441 URL: https://issues.jboss.org/browse/AS7-3441 Project: Application Server 7 Issue Type: Bug Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.2.0.Alpha1 See JPA Metrics > PersistenceUnitList. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
4
0 / 0

[JBoss JIRA] (JBWEB-227) Globally configure a Valve for the whole JBoss.

by Mo Zo (JIRA)

Mo Zo created JBWEB-227: --------------------------- Summary: Globally configure a Valve for the whole JBoss. Key: JBWEB-227 URL: https://issues.jboss.org/browse/JBWEB-227 Project: JBoss Web Issue Type: Feature Request Security Level: Public (Everyone can see) Environment: All Reporter: Mo Zo Assignee: Remy Maucherat Please provide a way to set and configure a Valve globally for all applications within a JBoss by using standard JBoss mechanisms like domain.xml, standalone.xml and DMR. Now it is only possible to configure it per application. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

2
1
0 / 0

[JBoss JIRA] (SASL-11) From RFC-2831 a realm name can contain whitespace, this means using space as the delimiter for possible realms is incorrect

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/SASL-11?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated SASL-11: --------------------------------- Fix Version/s: 1.0.1.CR1 (was: 1.0.0.GA) > From RFC-2831 a realm name can contain whitespace, this means using space as the delimiter for possible realms is incorrect > --------------------------------------------------------------------------------------------------------------------------- > > Key: SASL-11 > URL: https://issues.jboss.org/browse/SASL-11 > Project: JBoss SASL Provider > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.1.CR1 > > > By using space as the separator a single realm name that contains a space is split into two realms. > Either support quoted realm names if they contain a space or choose a different delimiter - (A different delimiter other than a control character may be difficult as the rest can appear in a realm name) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SASL-10) Pluggable nonce handling strategy

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/SASL-10?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated SASL-10: --------------------------------- Fix Version/s: 1.0.1.CR1 (was: 1.0.0.GA) > Pluggable nonce handling strategy > --------------------------------- > > Key: SASL-10 > URL: https://issues.jboss.org/browse/SASL-10 > Project: JBoss SASL Provider > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.1.CR1 > > > Implement a pluggable nonce handling strategy. > At the very least we need to be able to switch to using a SecureRandom instead of Random. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SASL-12) Digest Hex to byte mis-match

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/SASL-12?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated SASL-12: --------------------------------- Fix Version/s: 1.0.1.CR1 (was: 1.0.0.GA) > Digest Hex to byte mis-match > ---------------------------- > > Key: SASL-12 > URL: https://issues.jboss.org/browse/SASL-12 > Project: JBoss SASL Provider > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 1.0.0.Beta3 > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.1.CR1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
0
0 / 0

[JBoss JIRA] (AS7-3604) Release and upgrade org.jboss.sasl to GA

by Darran Lofthouse (JIRA)

Darran Lofthouse created AS7-3604: ------------------------------------- Summary: Release and upgrade org.jboss.sasl to GA Key: AS7-3604 URL: https://issues.jboss.org/browse/AS7-3604 Project: Application Server 7 Issue Type: Task Reporter: Darran Lofthouse Assignee: Darran Lofthouse Priority: Blocker Fix For: 7.1.0.Final -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
3
0 / 0

[JBoss JIRA] (SASL-28) Release JBoss SASL 1.0.0.GA

by Darran Lofthouse (JIRA)

Darran Lofthouse created SASL-28: ------------------------------------ Summary: Release JBoss SASL 1.0.0.GA Key: SASL-28 URL: https://issues.jboss.org/browse/SASL-28 Project: JBoss SASL Provider Issue Type: Task Security Level: Public (Everyone can see) Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.0.0.Beta10 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBSER-119) Ensure compatibility with Trove

by Christian Effertz (JIRA)

Ensure compatibility with Trove ------------------------------- Key: JBSER-119 URL: https://jira.jboss.org/jira/browse/JBSER-119 Project: JBoss Serialization Issue Type: Thirdparty Change Affects Versions: 1.0.3 GA Reporter: Christian Effertz Assignee: Clebert Suconic Fix For: 1.1.0 Beta The version of [Trove|http://trove4j.sourceforge.net] that is shipped with the latest version of JBoss Serialization is quite old. Trove has had a major release since it was bundled last time for Version 1.0.3 and seems to be facing a next major version 3.0. As it is stated in their release notes that they had some performance improvements and Bug Fixes I would assume that JBoss Serialization would profit in terms of stability and performance if using the newer versions. I will give it a try in our dev system, but it would be more comforting to get a statement if your testsuite turned green if using the newer version. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

2
2
0 / 0

[JBoss JIRA] (JGRP-1422) TP: reduce "no physical address for X; dropping message" warnings

by Bela Ban (JIRA)

Bela Ban created JGRP-1422: ------------------------------ Summary: TP: reduce "no physical address for X; dropping message" warnings Key: JGRP-1422 URL: https://issues.jboss.org/browse/JGRP-1422 Project: JGroups Issue Type: Enhancement Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.1 This warning is caused by A attempting to send a unicast message to B, but the physical (IP) address of B is not in the cache (TP.logical_addr_cache). The logical_addr_cache is populated at startup, during the discovery phase. However, when we have 20 members and (PING.)num_initial_members is 3, we'll return after 3 responses. If we for example have {A,B,C,D,E,F,G,H} with A being the coordinator, a new joiner X returns after reception of (say) discovery responses of F, B and G. If X next tries to send a JOIN request to A, it will fail and drop the (unicast) request as the IP address for A is not yet present. Event worse: if X attempts to invoke a unicast RPC to any member P for which it doesn't have the IP address, and does *not* send any more messages (e.g. in a separate thread to P), then the RPC will timeout, unless we use UNICAST, which - using a positive ack scheme - keeps retransmitting the request until P sends an ack. The problem is that - when we don't have an IP address for P - we send a discovery request to fetch the IP address, but *drop* the current request. There are 2 levels at which we can fix this problem: #1 Make sure we receive at least the IP address of the coordinator at startup This is done by making sure (in the above example) that A's IP address is part of the response set before we return from the discovery phase. Note that when we send a discovery request, everybody will reply, but if we return after reception of the replies from B, F and G, we won't have the coordinator's address to send a JOIN request to. So #1 makes sure that we only return after having the coordinator's IP address. Note that this can still lead to problems when trying to send a unicast message to a different member, whose IP address we don't yet have ! This is solved in #2 below. #2 When asking for the IP address of P, don't drop the current message to P, but loop for a short time until the address has been fetched We don't block here, but simply loop for a limited time, in order to wait for the IP address. In most cases, this is not even necessary because #1 reduces the chances of an IP address not being available, but if it is, usually fetching an IP address takes a few millisconds. Looping just reduces the chances that we have to run into a timeout with a blocking unicast RPC, or wait until stability flushes the pending unicast, causing it to be retransmitted. Note that we increase the wait time on every loop iteration, to prevent discovery storms. Plus, we also stagger the discovery request: if 2 threads T1 and T2 trigger a discovery at time 30 and 120 respectively, then T2 will *not* send a discovery request, as it also has the IP address by means of the discovery request triggered by T1. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2012