December 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SECURITY-777) Picketbox uses non-synchronized static maps

by Stefan Guilhen (JIRA)

[ https://issues.jboss.org/browse/SECURITY-777?page=com.atlassian.jira.plug... ] Stefan Guilhen resolved SECURITY-777. ------------------------------------- Fix Version/s: PicketBox_4_0_20.Final Resolution: Done Patch has been applied to PicketBox trunk > Picketbox uses non-synchronized static maps > ------------------------------------------- > > Key: SECURITY-777 > URL: https://issues.jboss.org/browse/SECURITY-777 > Project: PicketBox > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: PicketBox_4_0_20.Beta2 > Reporter: Stuart Douglas > Assignee: Stefan Guilhen > Fix For: PicketBox_4_0_20.Final > > Attachments: picketlink.diff > > > Picketbox uses quite a few static maps as global registries (yuck), and unfortunately they are not all thread safe, which can result in races as Wildfly starts security domains asynchronously. > Please see attached patch. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2448) Print IOR to a user specified file

by Stefan Guilhen (JIRA)

[ https://issues.jboss.org/browse/WFLY-2448?page=com.atlassian.jira.plugin.... ] Stefan Guilhen commented on WFLY-2448: -------------------------------------- I think this is a perfectly valid RFE so I encourage you to submit your patch > Print IOR to a user specified file > ---------------------------------- > > Key: WFLY-2448 > URL: https://issues.jboss.org/browse/WFLY-2448 > Project: WildFly > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: IIOP > Affects Versions: 8.0.0.Beta1 > Environment: Windows, Solaris, Linux > Reporter: Sumanth M S > Assignee: Stefan Guilhen > Priority: Minor > Fix For: 8.0.0.Final > > > Jboss AS prints Corba IOR on console or log file. Many applications look for a file at a predefined location from where it can read the IOR; as it is difficult to read IOR programatically from a log file or console. > An environment variable can be defined in standalone.conf to let the user specify the file location to which JBoss will print the IOR along with printing on the console. > The solution has been tried and seems working. Please let us know if the solution can be submitted. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1131) Narayana 5.0.0.CR2

by Jesper Pedersen (JIRA)

Jesper Pedersen created JBJCA-1131: -------------------------------------- Summary: Narayana 5.0.0.CR2 Key: JBJCA-1131 URL: https://issues.jboss.org/browse/JBJCA-1131 Project: IronJacamar Issue Type: Component Upgrade Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.1.3.Final -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1130) Track component updates

by Jesper Pedersen (JIRA)

Jesper Pedersen created JBJCA-1130: -------------------------------------- Summary: Track component updates Key: JBJCA-1130 URL: https://issues.jboss.org/browse/JBJCA-1130 Project: IronJacamar Issue Type: Task Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.1.3.Final -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1871) CLI module command doesn't allow cross platform resource paths

by Stan Silvert (JIRA)

[ https://issues.jboss.org/browse/WFLY-1871?page=com.atlassian.jira.plugin.... ] Stan Silvert resolved WFLY-1871. -------------------------------- Resolution: Done > CLI module command doesn't allow cross platform resource paths > -------------------------------------------------------------- > > Key: WFLY-1871 > URL: https://issues.jboss.org/browse/WFLY-1871 > Project: WildFly > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: CLI > Affects Versions: 8.0.0.Alpha4 > Reporter: Stan Silvert > Assignee: Stan Silvert > Fix For: 8.0.0.Final > > > The CLI module command has an argument called "resources". This argument allows you to specify one or more resources separated by the platform-specific path separator. The problem with this is that you can not create a platform-independent script that uses this resources argument. > I have not found a universal path separator character that would work. However, since the creator of the script knows the characters used in his path, we can allow him to specify his own separator. > As an enhancement, I propose to add an argument called "resourceDelimiter". If present, the ASModuleHandler class will use the user-defined delimiter instead of the platform-specific path separator character. > Example usage: > {noformat} > module add --name=org.foo --resources=firstResource.jar:secondResource.jar --resourceDelimiter=: --module-xml=foo-module.xml > {noformat} > The above command would work on Unix, Windows, or any other platform. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1749) Remove override for jgroups.bind_addr, jgroups.udp.mcast_addr, jgroups.udp.mcast_port

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1749?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-1749: --------------------------- Description: If we have {code:xml} <UDP bind_addr="${myapp.bind_addr:127.0.0.1}".../> {code} , then the default bind_addr is {{127.0.0.1}}. If we set {{-Dmyapp.bind_addr=1.2.3.4}} but also set {{-Djgroups.bind_addr=5.6.7.8}}, then *the latter system property always overrides the former*. This is bad, e.g. when we have multiple channels in the same JVM, where one channel uses {{myapp1.bind_addr}} and the other {{myapp2.bind_addr}}. If {{-Djgroups.bind_addr}} is set (e.g. by JBoss EAP), then we'll always use it rather than the different bind addresses ! Investigate whether we still need to use those overrides. Contact Brian Stansberry, IIRC he's the one who suggested this. SOLUTION: remove the _global_ system properties such as {{jgroups.bind_addr}}. was:Investigate whether we still need to use those overrides. Contact Brian Stansberry, IIRC he's the one who suggested this. > Remove override for jgroups.bind_addr, jgroups.udp.mcast_addr, jgroups.udp.mcast_port > ------------------------------------------------------------------------------------- > > Key: JGRP-1749 > URL: https://issues.jboss.org/browse/JGRP-1749 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 3.4.2, 3.5 > > > If we have > {code:xml} > <UDP bind_addr="${myapp.bind_addr:127.0.0.1}".../> > {code} > , then the default bind_addr is {{127.0.0.1}}. > If we set {{-Dmyapp.bind_addr=1.2.3.4}} but also set {{-Djgroups.bind_addr=5.6.7.8}}, then *the latter system property always overrides the former*. > This is bad, e.g. when we have multiple channels in the same JVM, where one channel uses {{myapp1.bind_addr}} and the other {{myapp2.bind_addr}}. If {{-Djgroups.bind_addr}} is set (e.g. by JBoss EAP), then we'll always use it rather than the different bind addresses ! > Investigate whether we still need to use those overrides. Contact Brian Stansberry, IIRC he's the one who suggested this. > SOLUTION: remove the _global_ system properties such as {{jgroups.bind_addr}}. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1738) @Property on setter doesn't expose the attr via probe.sh

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1738?page=com.atlassian.jira.plugin.... ] Bela Ban resolved JGRP-1738. ---------------------------- Resolution: Done Moved {{@Property}} to getter rather than setter > @Property on setter doesn't expose the attr via probe.sh > -------------------------------------------------------- > > Key: JGRP-1738 > URL: https://issues.jboss.org/browse/JGRP-1738 > Project: JGroups > Issue Type: Bug > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 3.5 > > > If we have > {noformat} > int attr; > @Property > public void setAttr(int val) {...} > {noformat} > then attr won't be exposed via probe.sh. It *is* exposed via JMX (jconsole) though. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-490) Domain Management Role Based Access Control

by Gopi Chand Uppala (JIRA)

[ https://issues.jboss.org/browse/WFLY-490?page=com.atlassian.jira.plugin.s... ] Gopi Chand Uppala commented on WFLY-490: ---------------------------------------- Brian, I thought this would be roled into EAP 6.2. Could you please confirm when this will be available? > Domain Management Role Based Access Control > ------------------------------------------- > > Key: WFLY-490 > URL: https://issues.jboss.org/browse/WFLY-490 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Blocker > Labels: Authorization > Fix For: 8.0.0.Final > > > Implement some coarse permissions for domain operations. Possibly allowing a break down for subsystem, profile, server, server-group - maybe read - write - execute. > Also consider confidentiality in exchange e.g. Can read metrics over http but must use https to add new server. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1738) @Property on setter doesn't expose the attr via probe.sh

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1738?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-1738: --------------------------- Fix Version/s: (was: 3.4.2) > @Property on setter doesn't expose the attr via probe.sh > -------------------------------------------------------- > > Key: JGRP-1738 > URL: https://issues.jboss.org/browse/JGRP-1738 > Project: JGroups > Issue Type: Bug > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 3.5 > > > If we have > {noformat} > int attr; > @Property > public void setAttr(int val) {...} > {noformat} > then attr won't be exposed via probe.sh. It *is* exposed via JMX (jconsole) though. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2681) HTTP Management Interface Content-Type header is broken

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-2681?page=com.atlassian.jira.plugin.... ] Stuart Douglas reassigned WFLY-2681: ------------------------------------ Assignee: Stuart Douglas (was: Brian Stansberry) > HTTP Management Interface Content-Type header is broken > ------------------------------------------------------- > > Key: WFLY-2681 > URL: https://issues.jboss.org/browse/WFLY-2681 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.CR1 > Reporter: Dino Tsoumakis > Assignee: Stuart Douglas > Fix For: 8.0.0.Final > > > *Problem:* > HTTP Domain Management Interfaces returns invalid Content-Type header: > {code} > Content-Type: application/json;utf-8 > {code} > This breaks management for lots of REST clients. > *Proposed solution:* > According to [W3C|https://www.w3.org/International/O-HTTP-charset] and [rfc2616|http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html#sec3.7] the Content-Type header should be: > {code} > Content-Type: application/json; charset=utf-8 > {code} > BTW: JBoss 7.1.1 behaviour is ok. It does not send any charset parameter at all. > *Example:* > Request contains the following headers: > {code} > 3 > Accept: application/json > 3 > Content-Type: application/json > ... > {code} > Wildfly 8.0.0.CR1 response after digest authentication is: > {code} > 4 < 200 > 4 < Authentication-Info: nextnonce="EB9WbpMrUuwNMTM4NzY3MDc2NzAxMgXaHXwaKEWPxbxUj1ihuOg=" > 4 < Connection: keep-alive > 4 < Content-Type: application/json;utf-8 > 4 < Transfer-Encoding: chunked > {code} > JBoss 7.1.1 response after digest authentication is: > {code} > 4 < 200 > 4 < Content-type: application/json > 4 < Date: Sat, 21 Dec 2013 23:48:36 GMT > 4 < Transfer-encoding: chunked > {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

12 years, 7 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 December 2013