You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hivemind.apache.org by "Renat Zubairov (JIRA)" <hi...@jakarta.apache.org> on 2006/08/11 09:01:14 UTC
[jira] Created: (HIVEMIND-181) Hivmind will not work in with
security enforcments due to bug in Javassist
Hivmind will not work in with security enforcments due to bug in Javassist
--------------------------------------------------------------------------
Key: HIVEMIND-181
URL: http://issues.apache.org/jira/browse/HIVEMIND-181
Project: HiveMind
Issue Type: Bug
Environment: IBM WebSphere 5 with Security ON
IBM JVM
Reporter: Renat Zubairov
Priority: Critical
Due to the bug in Javassist, ProtectionDomain wasn't associated with generated classes, see JIRRA from Javassist:
http://jira.jboss.com/jira/browse/JASSIST-23
This bug stops from executing any Hivemind based application (e.g. Tapestry) on the any environment with active SecurityManager.
Unfortunately for proper fixing of this bug some changes within the Hivemind are required, such as (I expect)
1. Switch to the latest Javassist
2. Change all "old" method calls to the new one with additional parameter - Hivemind protection domain.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (HIVEMIND-181) Hivmind will not work in with
security enforcments due to bug in Javassist
Posted by "Jonas Maurus (JIRA)" <hi...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/HIVEMIND-181?page=comments#action_12455186 ]
Jonas Maurus commented on HIVEMIND-181:
---------------------------------------
As stated in HIVEMIND-192 and at http://jira.jboss.com/jira/browse/JASSIST-23 the bug in Javassist has been fixed.
> Hivmind will not work in with security enforcments due to bug in Javassist
> --------------------------------------------------------------------------
>
> Key: HIVEMIND-181
> URL: http://issues.apache.org/jira/browse/HIVEMIND-181
> Project: HiveMind
> Issue Type: Bug
> Environment: IBM WebSphere 5 with Security ON
> IBM JVM
> Reporter: Renat Zubairov
> Priority: Critical
>
> Due to the bug in Javassist, ProtectionDomain wasn't associated with generated classes, see JIRRA from Javassist:
> http://jira.jboss.com/jira/browse/JASSIST-23
> This bug stops from executing any Hivemind based application (e.g. Tapestry) on the any environment with active SecurityManager.
> Unfortunately for proper fixing of this bug some changes within the Hivemind are required, such as (I expect)
> 1. Switch to the latest Javassist
> 2. Change all "old" method calls to the new one with additional parameter - Hivemind protection domain.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (HIVEMIND-181) Hivmind will not work in with
security enforcments due to bug in Javassist
Posted by "Jonas Maurus (JIRA)" <hi...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/HIVEMIND-181?page=comments#action_12455167 ]
Jonas Maurus commented on HIVEMIND-181:
---------------------------------------
This is now a duplicate of HIVEMIND-192 where a detailed solution for this problem has been proposed.
> Hivmind will not work in with security enforcments due to bug in Javassist
> --------------------------------------------------------------------------
>
> Key: HIVEMIND-181
> URL: http://issues.apache.org/jira/browse/HIVEMIND-181
> Project: HiveMind
> Issue Type: Bug
> Environment: IBM WebSphere 5 with Security ON
> IBM JVM
> Reporter: Renat Zubairov
> Priority: Critical
>
> Due to the bug in Javassist, ProtectionDomain wasn't associated with generated classes, see JIRRA from Javassist:
> http://jira.jboss.com/jira/browse/JASSIST-23
> This bug stops from executing any Hivemind based application (e.g. Tapestry) on the any environment with active SecurityManager.
> Unfortunately for proper fixing of this bug some changes within the Hivemind are required, such as (I expect)
> 1. Switch to the latest Javassist
> 2. Change all "old" method calls to the new one with additional parameter - Hivemind protection domain.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (HIVEMIND-181) Hivmind will not work in with
security enforcments due to bug in Javassist
Posted by "Renat Zubairov (JIRA)" <hi...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/HIVEMIND-181?page=comments#action_12455188 ]
Renat Zubairov commented on HIVEMIND-181:
-----------------------------------------
This bug require changes in the hivemind - first update the Javassist version, second use different, more correct helper method of the Javassist.
> Hivmind will not work in with security enforcments due to bug in Javassist
> --------------------------------------------------------------------------
>
> Key: HIVEMIND-181
> URL: http://issues.apache.org/jira/browse/HIVEMIND-181
> Project: HiveMind
> Issue Type: Bug
> Environment: IBM WebSphere 5 with Security ON
> IBM JVM
> Reporter: Renat Zubairov
> Priority: Critical
>
> Due to the bug in Javassist, ProtectionDomain wasn't associated with generated classes, see JIRRA from Javassist:
> http://jira.jboss.com/jira/browse/JASSIST-23
> This bug stops from executing any Hivemind based application (e.g. Tapestry) on the any environment with active SecurityManager.
> Unfortunately for proper fixing of this bug some changes within the Hivemind are required, such as (I expect)
> 1. Switch to the latest Javassist
> 2. Change all "old" method calls to the new one with additional parameter - Hivemind protection domain.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (HIVEMIND-181) Hivmind will not work in with
security enforcments due to bug in Javassist
Posted by "Renat Zubairov (JIRA)" <hi...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/HIVEMIND-181?page=comments#action_12427455 ]
Renat Zubairov commented on HIVEMIND-181:
-----------------------------------------
Sorry, forgot to set.
Component: Framework (I guess)
Affects Version: 1.1.1
> Hivmind will not work in with security enforcments due to bug in Javassist
> --------------------------------------------------------------------------
>
> Key: HIVEMIND-181
> URL: http://issues.apache.org/jira/browse/HIVEMIND-181
> Project: HiveMind
> Issue Type: Bug
> Environment: IBM WebSphere 5 with Security ON
> IBM JVM
> Reporter: Renat Zubairov
> Priority: Critical
>
> Due to the bug in Javassist, ProtectionDomain wasn't associated with generated classes, see JIRRA from Javassist:
> http://jira.jboss.com/jira/browse/JASSIST-23
> This bug stops from executing any Hivemind based application (e.g. Tapestry) on the any environment with active SecurityManager.
> Unfortunately for proper fixing of this bug some changes within the Hivemind are required, such as (I expect)
> 1. Switch to the latest Javassist
> 2. Change all "old" method calls to the new one with additional parameter - Hivemind protection domain.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (HIVEMIND-181) Hivmind will not work in with
security enforcments due to bug in Javassist
Posted by "Johan Lindquist (JIRA)" <hi...@jakarta.apache.org>.
[ https://issues.apache.org/jira/browse/HIVEMIND-181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Johan Lindquist updated HIVEMIND-181:
-------------------------------------
Attachment: hivemind-181-192.patch
The attached patch resolves the issues about protection domain. Not sure if the choice of using the HiveMindClassPool class as the default provider of said domain is correct.
> Hivmind will not work in with security enforcments due to bug in Javassist
> --------------------------------------------------------------------------
>
> Key: HIVEMIND-181
> URL: https://issues.apache.org/jira/browse/HIVEMIND-181
> Project: HiveMind
> Issue Type: Bug
> Environment: IBM WebSphere 5 with Security ON
> IBM JVM
> Reporter: Renat Zubairov
> Priority: Critical
> Attachments: hivemind-181-192.patch
>
>
> Due to the bug in Javassist, ProtectionDomain wasn't associated with generated classes, see JIRRA from Javassist:
> http://jira.jboss.com/jira/browse/JASSIST-23
> This bug stops from executing any Hivemind based application (e.g. Tapestry) on the any environment with active SecurityManager.
> Unfortunately for proper fixing of this bug some changes within the Hivemind are required, such as (I expect)
> 1. Switch to the latest Javassist
> 2. Change all "old" method calls to the new one with additional parameter - Hivemind protection domain.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.