May 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBCLUSTER-269) AbstractJBossCacheService getSessionIds() misses dead backup regions

by Brian Stansberry (JIRA)

AbstractJBossCacheService getSessionIds() misses dead backup regions -------------------------------------------------------------------- Key: JBCLUSTER-269 URL: https://jira.jboss.org/jira/browse/JBCLUSTER-269 Project: JBoss Clustering Issue Type: Bug Security Level: Public (Everyone can see) Components: HA-Server-Cache-JBC Affects Versions: HA-Server-Cache-JBC 2.1.2.GA, HA-Server-Cache-JBC 2.0.1.GA , HA-Server-Cache-JBC 2.2.0.Final Reporter: Brian Stansberry Assignee: Brian Stansberry The algorithm for searching for session ids does not take into account that the Fqn for buddies whose name ends with :DEAD (i.e. buddies that JBC knows are no longer in the group) include an extra element. Effect is getSessionIds() does not return ids for sessions stored under such trees. Effect of this is when a session manager starts, it gets an incomplete listing of session ids. Affects of this are: 1) Some incorrect session count statistics through the JMX interface. 2) The sessions that are missed will not be passivated or expired by the background cleanup task. Such sessions will still be available if accessed by a user request. Fix is to properly search the dead buddy backup trees. -- 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

16 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBJCA-324) Javassist 3.12.0.GA

by Jesper Pedersen (JIRA)

Javassist 3.12.0.GA ------------------- Key: JBJCA-324 URL: https://jira.jboss.org/jira/browse/JBJCA-324 Project: JBoss JCA Issue Type: Component Upgrade Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.0.Alpha12 -- 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

16 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBJCA-323) Papaki 1.0.0.Beta3

by Jesper Pedersen (JIRA)

Papaki 1.0.0.Beta3 ------------------ Key: JBJCA-323 URL: https://jira.jboss.org/jira/browse/JBJCA-323 Project: JBoss JCA Issue Type: Component Upgrade Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.0.Alpha12 -- 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

16 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBANN-52) Papaki 1.0.0.Beta3

by Jesper Pedersen (JIRA)

Papaki 1.0.0.Beta3 ------------------ Key: JBANN-52 URL: https://jira.jboss.org/jira/browse/JBANN-52 Project: Papaki Issue Type: Release Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.0.Beta3 -- 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

16 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBANN-49) Javassist 3.12.0.GA

by Jesper Pedersen (JIRA)

Javassist 3.12.0.GA ------------------- Key: JBANN-49 URL: https://jira.jboss.org/jira/browse/JBANN-49 Project: Papaki Issue Type: Thirdparty Change Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.0.Beta3 -- 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

16 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBANN-50) APIViz 1.3.1.GA

by Jesper Pedersen (JIRA)

APIViz 1.3.1.GA --------------- Key: JBANN-50 URL: https://jira.jboss.org/jira/browse/JBANN-50 Project: Papaki Issue Type: Thirdparty Change Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.0.Beta3 -- 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

16 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBANN-51) JUnit 4.8.1

by Jesper Pedersen (JIRA)

JUnit 4.8.1 ----------- Key: JBANN-51 URL: https://jira.jboss.org/jira/browse/JBANN-51 Project: Papaki Issue Type: Thirdparty Change Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.0.Beta3 -- 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

16 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-2437) Add drools examples to the default build and remove the foxtrot and forms jars from subversion

by Geoffrey De Smet (JIRA)

Add drools examples to the default build and remove the foxtrot and forms jars from subversion ---------------------------------------------------------------------------------------------- Key: JBRULES-2437 URL: https://jira.jboss.org/jira/browse/JBRULES-2437 Project: Drools Issue Type: Task Security Level: Public (Everyone can see) Components: All Affects Versions: 5.1.0.M1 Reporter: Geoffrey De Smet Assignee: Geoffrey De Smet Fix For: FUTURE drools/drools-examples/drools-examples-drl/lib/foxtrot-2.0.jar shouldn't be in subversion (forms neither) the build.xml for ant can also be removed check the assembly of the examples too add the examples to the default build -- 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

16 years, 2 months

1
3
0 / 0

[JBoss JIRA] Resolved: (JBWEB-141) Servlet Filter against CSRF

by Remy Maucherat (JIRA)

[ https://jira.jboss.org/jira/browse/JBWEB-141?page=com.atlassian.jira.plug... ] Remy Maucherat resolved JBWEB-141. ---------------------------------- Fix Version/s: JBossWeb-3.0.0.Beta6 Resolution: Done For XSS, if you are talking about a well defined set of patterns, you might be able to create a set of mod_rewrite rules. They should then work just fine with the rewrite valve. If that's not enough, then create a new JIRA on XSS. > Servlet Filter against CSRF > --------------------------- > > Key: JBWEB-141 > URL: https://jira.jboss.org/jira/browse/JBWEB-141 > Project: JBoss Web > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Marc Schoenefeld > Assignee: Remy Maucherat > Priority: Minor > Fix For: JBossWeb-3.0.0.Beta6 > > > Cross-Site scripting and cross-site request forgery attacks are common threat to every web application. > So a common solution offered by the http server is helpful to raise the default protection level. > A servlet filter will help to > a) allow/block requests for a set of XSS regex patterns (per default blacklist suspicious parameter patterns, and optionally whitelist valid requests for well-known applications) > b) allow/block requests that fulfil the criteria for being a forged request (failing nonce compare), this will need a javascript helper on the client side, to transparently protect existing applications to provide the shared secret in the session . -- 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

16 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWEB-141) Servlet Filter against CSRF

by Remy Maucherat (JIRA)

[ https://jira.jboss.org/jira/browse/JBWEB-141?page=com.atlassian.jira.plug... ] Remy Maucherat updated JBWEB-141: --------------------------------- Summary: Servlet Filter against CSRF (was: Servlet Filter against XSS) > Servlet Filter against CSRF > --------------------------- > > Key: JBWEB-141 > URL: https://jira.jboss.org/jira/browse/JBWEB-141 > Project: JBoss Web > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Marc Schoenefeld > Assignee: Remy Maucherat > Priority: Minor > > Cross-Site scripting and cross-site request forgery attacks are common threat to every web application. > So a common solution offered by the http server is helpful to raise the default protection level. > A servlet filter will help to > a) allow/block requests for a set of XSS regex patterns (per default blacklist suspicious parameter patterns, and optionally whitelist valid requests for well-known applications) > b) allow/block requests that fulfil the criteria for being a forged request (failing nonce compare), this will need a javascript helper on the client side, to transparently protect existing applications to provide the shared secret in the session . -- 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

16 years, 2 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 May 2010