April 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SECURITY-821) SPNEGOSocket does not throw Exception in case it fails to establish GSSContext

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-821?page=com.atlassian.jira.plug... ] RH Bugzilla Integration updated SECURITY-821: --------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1088792, https://bugzilla.redhat.com/show_bug.cgi?id=1088793 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1088792) > SPNEGOSocket does not throw Exception in case it fails to establish GSSContext > ------------------------------------------------------------------------------ > > Key: SECURITY-821 > URL: https://issues.jboss.org/browse/SECURITY-821 > Project: PicketBox > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Negotiation > Affects Versions: Negotiation_2_1_5, Negotiation_2_2_7, Negotiation_2_3_0_Final > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > Fix For: Negotiation_2_1_6, Negotiation_2_2_8, Negotiation_2_3_1_Final > > > Point of failure: https://github.com/wildfly/jboss-negotiation/blob/master/jboss-negotiatio... > Socket in mentioned versions log error and allow connection to be up. This is a cause of hangup in case of proxy lookup( atleast in EAP5 - JBPAPP-10748 ) > Code should terminate connection and throw exception upstream, in case login/logout(?) failure. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3241) KDC server does not bind to correct address

by Dominik Pospisil (JIRA)

[ https://issues.jboss.org/browse/WFLY-3241?page=com.atlassian.jira.plugin.... ] Dominik Pospisil commented on WFLY-3241: ---------------------------------------- https://github.com/wildfly/wildfly/pull/6154 > KDC server does not bind to correct address > ------------------------------------------- > > Key: WFLY-3241 > URL: https://issues.jboss.org/browse/WFLY-3241 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Test Suite > Affects Versions: 8.1.0.CR1 > Reporter: Dominik Pospisil > Assignee: Dominik Pospisil > -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3241) KDC server does not bind to correct address

by Dominik Pospisil (JIRA)

[ https://issues.jboss.org/browse/WFLY-3241?page=com.atlassian.jira.plugin.... ] Dominik Pospisil resolved WFLY-3241. ------------------------------------ Resolution: Done > KDC server does not bind to correct address > ------------------------------------------- > > Key: WFLY-3241 > URL: https://issues.jboss.org/browse/WFLY-3241 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Test Suite > Affects Versions: 8.1.0.CR1 > Reporter: Dominik Pospisil > Assignee: Dominik Pospisil > -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-821) SPNEGOSocket does not throw Exception in case it fails to establish GSSContext

by Bartosz Baranowski (JIRA)

[ https://issues.jboss.org/browse/SECURITY-821?page=com.atlassian.jira.plug... ] Bartosz Baranowski commented on SECURITY-821: --------------------------------------------- PRs: 2.1.x : https://github.com/wildfly/jboss-negotiation/pull/10 2.2.x : https://github.com/wildfly/jboss-negotiation/pull/7 2.x : https://github.com/wildfly/jboss-negotiation/pull/8 > SPNEGOSocket does not throw Exception in case it fails to establish GSSContext > ------------------------------------------------------------------------------ > > Key: SECURITY-821 > URL: https://issues.jboss.org/browse/SECURITY-821 > Project: PicketBox > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Negotiation > Affects Versions: Negotiation_2_1_5, Negotiation_2_2_7, Negotiation_2_3_0_Final > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > Fix For: Negotiation_2_1_6, Negotiation_2_2_8, Negotiation_2_3_1_Final > > > Point of failure: https://github.com/wildfly/jboss-negotiation/blob/master/jboss-negotiatio... > Socket in mentioned versions log error and allow connection to be up. This is a cause of hangup in case of proxy lookup( atleast in EAP5 - JBPAPP-10748 ) > Code should terminate connection and throw exception upstream, in case login/logout(?) failure. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-821) SPNEGOSocket does not throw Exception in case it fails to establish GSSContext

by Bartosz Baranowski (JIRA)

[ https://issues.jboss.org/browse/SECURITY-821?page=com.atlassian.jira.plug... ] Bartosz Baranowski updated SECURITY-821: ---------------------------------------- Summary: SPNEGOSocket does not throw Exception in case it fails to establish GSSContext (was: SPNEGOSocket does not throw Exception in case it fails to establiosh GSSContext) > SPNEGOSocket does not throw Exception in case it fails to establish GSSContext > ------------------------------------------------------------------------------ > > Key: SECURITY-821 > URL: https://issues.jboss.org/browse/SECURITY-821 > Project: PicketBox > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Negotiation > Affects Versions: Negotiation_2_1_5, Negotiation_2_2_7, Negotiation_2_3_0_Final > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > Fix For: Negotiation_2_1_6, Negotiation_2_2_8, Negotiation_2_3_1_Final > > > Point of failure: https://github.com/wildfly/jboss-negotiation/blob/master/jboss-negotiatio... > Socket in mentioned versions log error and allow connection to be up. This is a cause of hangup in case of proxy lookup( atleast in EAP5 - JBPAPP-10748 ) > Code should terminate connection and throw exception upstream, in case login/logout(?) failure. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-821) SPNEGOSocket does not throw Exception in case it fails to establiosh GSSContext

by Bartosz Baranowski (JIRA)

[ https://issues.jboss.org/browse/SECURITY-821?page=com.atlassian.jira.plug... ] Bartosz Baranowski commented on SECURITY-821: --------------------------------------------- SPNEGOServerSocket seems to throw IOE in such case. > SPNEGOSocket does not throw Exception in case it fails to establiosh GSSContext > ------------------------------------------------------------------------------- > > Key: SECURITY-821 > URL: https://issues.jboss.org/browse/SECURITY-821 > Project: PicketBox > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Negotiation > Affects Versions: Negotiation_2_1_5, Negotiation_2_2_7, Negotiation_2_3_0_Final > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > Fix For: Negotiation_2_1_6, Negotiation_2_2_8, Negotiation_2_3_1_Final > > > Point of failure: https://github.com/wildfly/jboss-negotiation/blob/master/jboss-negotiatio... > Socket in mentioned versions log error and allow connection to be up. This is a cause of hangup in case of proxy lookup( atleast in EAP5 - JBPAPP-10748 ) > Code should terminate connection and throw exception upstream, in case login/logout(?) failure. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-821) SPNEGOSocket does not throw Exception in case it fails to establiosh GSSContext

by Bartosz Baranowski (JIRA)

Bartosz Baranowski created SECURITY-821: ------------------------------------------- Summary: SPNEGOSocket does not throw Exception in case it fails to establiosh GSSContext Key: SECURITY-821 URL: https://issues.jboss.org/browse/SECURITY-821 Project: PicketBox Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Negotiation Affects Versions: Negotiation_2_3_0_Final, Negotiation_2_2_7, Negotiation_2_1_5 Reporter: Bartosz Baranowski Assignee: Darran Lofthouse Fix For: Negotiation_2_1_6, Negotiation_2_2_8, Negotiation_2_3_1_Final Point of failure: https://github.com/wildfly/jboss-negotiation/blob/master/jboss-negotiatio... Socket in mentioned versions log error and allow connection to be up. This is a cause of hangup in case of proxy lookup( atleast in EAP5 - JBPAPP-10748 ) Code should terminate connection and throw exception upstream, in case login/logout(?) failure. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-821) SPNEGOSocket does not throw Exception in case it fails to establiosh GSSContext

by Bartosz Baranowski (JIRA)

[ https://issues.jboss.org/browse/SECURITY-821?page=com.atlassian.jira.plug... ] Bartosz Baranowski reassigned SECURITY-821: ------------------------------------------- Assignee: Bartosz Baranowski (was: Darran Lofthouse) > SPNEGOSocket does not throw Exception in case it fails to establiosh GSSContext > ------------------------------------------------------------------------------- > > Key: SECURITY-821 > URL: https://issues.jboss.org/browse/SECURITY-821 > Project: PicketBox > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Negotiation > Affects Versions: Negotiation_2_1_5, Negotiation_2_2_7, Negotiation_2_3_0_Final > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > Fix For: Negotiation_2_1_6, Negotiation_2_2_8, Negotiation_2_3_1_Final > > > Point of failure: https://github.com/wildfly/jboss-negotiation/blob/master/jboss-negotiatio... > Socket in mentioned versions log error and allow connection to be up. This is a cause of hangup in case of proxy lookup( atleast in EAP5 - JBPAPP-10748 ) > Code should terminate connection and throw exception upstream, in case login/logout(?) failure. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1820) XML schema broken for AUTH

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1820?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-1820: -------------------------------- Perhaps this can be combined with JGRP-1828 > XML schema broken for AUTH > -------------------------- > > Key: JGRP-1820 > URL: https://issues.jboss.org/browse/JGRP-1820 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.4.1 > Reporter: Dennis Reed > Assignee: Bela Ban > Priority: Minor > Fix For: 3.5 > > > The XML schema does not pass validation for AUTH. > AUTH merges in properties for the pluggable auth_class, which are not currently included in the schema. > For example the fixed_members_value when using FixedMembershipToken is not included in the schema and fails validation: > <AUTH auth_class="org.jgroups.auth.FixedMembershipToken" > fixed_members_value="localhost/7900"> > </AUTH> -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1827) Forked channel requires udp.xml file

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1827?page=com.atlassian.jira.plugin.... ] Bela Ban resolved JGRP-1827. ---------------------------- Resolution: Done > Forked channel requires udp.xml file > ------------------------------------ > > Key: JGRP-1827 > URL: https://issues.jboss.org/browse/JGRP-1827 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.4.1 > Environment: Android > Reporter: Jim Thomas > Assignee: Bela Ban > Priority: Minor > Fix For: 3.4.4, 3.5 > > Attachments: bla2.java, fork-stacks.xml, main.xml > > > An exception is thrown when creating a fork channel if the stack file name is something other than udp.xml (in my case main.xml): > final JChannel mainChannel = new JChannel("main.xml"); > final ForkChannel mbChannel = new ForkChannel(mainChannel, > "main", "fork-mb"); > 4-09 17:33:38.270: W/System.err(5478): java.io.FileNotFoundException: JGRP000003: file "udp.xml" not found > 04-09 17:33:38.270: W/System.err(5478): at org.jgroups.conf.ConfiguratorFactory.getXmlConfigurator(ConfiguratorFactory.java:211) > 04-09 17:33:38.270: W/System.err(5478): at org.jgroups.conf.ConfiguratorFactory.getStackConfigurator(ConfiguratorFactory.java:102) > 04-09 17:33:38.270: W/System.err(5478): at org.jgroups.JChannel.<init>(JChannel.java:172) > 04-09 17:33:38.270: W/System.err(5478): at org.jgroups.JChannel.<init>(JChannel.java:123) > 04-09 17:33:38.270: W/System.err(5478): at org.jgroups.fork.ForkChannel.<init>(ForkChannel.java:75) > 04-09 17:33:38.270: W/System.err(5478): at org.jgroups.fork.ForkChannel.<init>(ForkChannel.java:118) > 04-09 17:33:38.270: W/System.err(5478): at com.novawurks.jgroupstest.JGroupsTestActivity$JGroupsSetupThread.run(JGroupsTestActivity.java:119) > If I have the stack named udp.xml then the exception is not thrown and everything works as expected. If I make a copy of main.xml named udp.xml (so both files are present) the exception is not thrown and everything works as expected. > Contents of main.xml / udp.xml : > {code:xml} > <config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xmlns="urn:org:jgroups" > xsi:schemaLocation="urn:org:jgroups http://www.jgroups.org/schema/JGroups-3.3.xsd" > > <UDP > enable_diagnostics="true" > ip_mcast="true" > ip_ttl="${jgroups.udp.ip_ttl:8}" > loopback="true" > max_bundle_size="1400" > max_bundle_timeout="5" > mcast_port="${jgroups.udp.mcast_port:45588}" > mcast_recv_buf_size="200K" > mcast_send_buf_size="200K" > oob_thread_pool.enabled="true" > oob_thread_pool.keep_alive_time="5000" > oob_thread_pool.max_threads="8" > oob_thread_pool.min_threads="1" > oob_thread_pool.queue_enabled="false" > oob_thread_pool.queue_max_size="100" > oob_thread_pool.rejection_policy="discard" > thread_naming_pattern="cl" > thread_pool.enabled="true" > thread_pool.keep_alive_time="5000" > thread_pool.max_threads="8" > thread_pool.min_threads="2" > thread_pool.queue_enabled="true" > thread_pool.queue_max_size="10000" > thread_pool.rejection_policy="discard" > timer.keep_alive_time="3000" > timer.max_threads="10" > timer.min_threads="4" > timer.queue_max_size="500" > timer_type="new3" > tos="8" > ucast_recv_buf_size="200K" > ucast_send_buf_size="200K" /> > <PING /> > <MERGE2 > max_interval="30000" > min_interval="10000" /> > <FD_SOCK /> > <FD_ALL /> > <VERIFY_SUSPECT timeout="1500" /> > <BARRIER /> > <pbcast.NAKACK2 > discard_delivered_msgs="true" > max_msg_batch_size="500" > use_mcast_xmit="false" > xmit_interval="500" > xmit_table_max_compaction_time="30000" > xmit_table_msgs_per_row="2000" > xmit_table_num_rows="100" /> > <UNICAST3 > conn_expiry_timeout="0" > max_msg_batch_size="500" > xmit_interval="500" > xmit_table_max_compaction_time="60000" > xmit_table_msgs_per_row="2000" > xmit_table_num_rows="100" /> > <pbcast.STABLE > desired_avg_gossip="50000" > max_bytes="4M" > stability_delay="1000" /> > <pbcast.GMS > join_timeout="3000" > print_local_addr="true" > view_bundling="true" /> > <UFC > max_credits="2M" > min_threshold="0.4" /> > <MFC > max_credits="2M" > min_threshold="0.4" /> > <FRAG frag_size="1000" /> > <pbcast.STATE_TRANSFER /> > <FORK> > <fork-stack id="main" > > <config> > <CENTRAL_LOCK num_backups="2" /> > </config> > </fork-stack> > <fork-stack id="lock" > > <config> > <CENTRAL_LOCK num_backups="2" /> > <STATS /> > </config> > </fork-stack> > </FORK> > </config> > {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, 3 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 April 2014