[JBoss JIRA] Created: (JASSIST-23) Java 2 Security ProtiectionDomain is not associated with new generated classes

[JBoss JIRA] Updated: (JBAOP-37)...

[JBoss JIRA] Updated:...

Renat Zubairov (JIRA)

Tuesday, 18 July 2006 Tue, 18 Jul '06

10:27 a.m.

Java 2 Security ProtiectionDomain is not associated with new generated classes ------------------------------------------------------------------------------ Key: JASSIST-23 URL: http://jira.jboss.com/jira/browse/JASSIST-23 Project: Javassist Issue Type: Bug Environment: IBM WebSphere 5.1 with J2EE Security ON, Javassist 3.0, Tapestry 4.1, HiveMind 1.1.1 Reporter: Renat Zubairov Assigned To: Shigeru Chiba Priority: Blocker Attachments: exception.txt Classes that are generated using Javassist have no associated protection domain therefore it is not possible for JVM to assign permissions based on the static JAR files names, this is severe problem because it is not possible to grant permissions, hence all permissions are vorbidden, since that nothing works. Javassist is used by HiveMind to generate proxy classes for it's services, an see the stack trace (in attachment) the generated classes can't be associated with any ProtectionDomain, therefore _any Javassist supported application is impossble to start under strict security in Java_. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

Show replies by date

Renat Zubairov (JIRA)

Tuesday, 18 July Tue, 18 Jul

10:27 a.m.

New subject: [JBoss JIRA] Updated: (JASSIST-23) Java 2 Security ProtiectionDomain is not associated with new generated classes

[ http://jira.jboss.com/jira/browse/JASSIST-23?page=all ] Renat Zubairov updated JASSIST-23: ---------------------------------- Attachment: exception.txt Exception stack trace where visible that generated code have no code base.

...

Java 2 Security ProtiectionDomain is not associated with new generated classes ------------------------------------------------------------------------------ Key: JASSIST-23 URL: http://jira.jboss.com/jira/browse/JASSIST-23 Project: Javassist Issue Type: Bug Environment: IBM WebSphere 5.1 with J2EE Security ON, Javassist 3.0, Tapestry 4.1, HiveMind 1.1.1 Reporter: Renat Zubairov Assigned To: Shigeru Chiba Priority: Blocker Attachments: exception.txt Original Estimate: 3 hours Remaining Estimate: 3 hours Classes that are generated using Javassist have no associated protection domain therefore it is not possible for JVM to assign permissions based on the static JAR files names, this is severe problem because it is not possible to grant permissions, hence all permissions are vorbidden, since that nothing works. Javassist is used by HiveMind to generate proxy classes for it's services, an see the stack trace (in attachment) the generated classes can't be associated with any ProtectionDomain, therefore _any Javassist supported application is impossble to start under strict security in Java_.

-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

Renat Zubairov (JIRA)

10:29 a.m.

New subject: [JBoss JIRA] Updated: (JASSIST-23) Java 2 Security ProtiectionDomain is not associated with new generated classes

[ http://jira.jboss.com/jira/browse/JASSIST-23?page=all ] Renat Zubairov updated JASSIST-23: ---------------------------------- JBoss Forum Reference: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=86917

...

Java 2 Security ProtiectionDomain is not associated with new generated classes ------------------------------------------------------------------------------ Key: JASSIST-23 URL: http://jira.jboss.com/jira/browse/JASSIST-23 Project: Javassist Issue Type: Bug Environment: IBM WebSphere 5.1 with J2EE Security ON, Javassist 3.0, Tapestry 4.1, HiveMind 1.1.1 Reporter: Renat Zubairov Assigned To: Shigeru Chiba Priority: Blocker Attachments: exception.txt Original Estimate: 3 hours Remaining Estimate: 3 hours Classes that are generated using Javassist have no associated protection domain therefore it is not possible for JVM to assign permissions based on the static JAR files names, this is severe problem because it is not possible to grant permissions, hence all permissions are vorbidden, since that nothing works. Javassist is used by HiveMind to generate proxy classes for it's services, an see the stack trace (in attachment) the generated classes can't be associated with any ProtectionDomain, therefore _any Javassist supported application is impossble to start under strict security in Java_.

Renat Zubairov (JIRA)

2:37 p.m.

New subject: [JBoss JIRA] Commented: (JASSIST-23) Java 2 Security ProtiectionDomain is not associated with new generated classes

[ http://jira.jboss.com/jira/browse/JASSIST-23?page=comments#action_12339747 ] Renat Zubairov commented on JASSIST-23: --------------------------------------- What I like about Javassist is a vibrant and visible community arround... Anyway I found a solution for the problem and it is clear a very simple mistake made by authors of the CtClass object, when they are using classloader API they ignore security concerns, hence I had this problem now. There are at least two methods defineClass, one is a complete security ignorance, another one is with specification of the ProtectionDomain. I'll post a more proper solution shortly.

...

Java 2 Security ProtiectionDomain is not associated with new generated classes ------------------------------------------------------------------------------ Key: JASSIST-23 URL: http://jira.jboss.com/jira/browse/JASSIST-23 Project: Javassist Issue Type: Bug Environment: IBM WebSphere 5.1 with J2EE Security ON, Javassist 3.0, Tapestry 4.1, HiveMind 1.1.1 Reporter: Renat Zubairov Assigned To: Shigeru Chiba Priority: Blocker Attachments: exception.txt Original Estimate: 3 hours Remaining Estimate: 3 hours Classes that are generated using Javassist have no associated protection domain therefore it is not possible for JVM to assign permissions based on the static JAR files names, this is severe problem because it is not possible to grant permissions, hence all permissions are vorbidden, since that nothing works. Javassist is used by HiveMind to generate proxy classes for it's services, an see the stack trace (in attachment) the generated classes can't be associated with any ProtectionDomain, therefore _any Javassist supported application is impossble to start under strict security in Java_.

Shigeru Chiba (JIRA)

Sunday, 6 August Sun, 6 Aug

5:30 p.m.

New subject: [JBoss JIRA] Commented: (JASSIST-23) Java 2 Security ProtiectionDomain is not associated with new generated classes

[ http://jira.jboss.com/jira/browse/JASSIST-23?page=comments#action_12340714 ] Shigeru Chiba commented on JASSIST-23: -------------------------------------- Basically, Javassist provides a byte stream of a modified class file. How it is loaded is the responsiblity of the clients such as HiveMind. Although Javassist provides a covenient function for loading it by a simple class loader, the clients should use their own class loaders if they need some application-specific requirements. Do you know how HiveMind load classes generated by Javassist? Thanks!

...

Java 2 Security ProtiectionDomain is not associated with new generated classes ------------------------------------------------------------------------------ Key: JASSIST-23 URL: http://jira.jboss.com/jira/browse/JASSIST-23 Project: Javassist Issue Type: Bug Environment: IBM WebSphere 5.1 with J2EE Security ON, Javassist 3.0, Tapestry 4.1, HiveMind 1.1.1 Reporter: Renat Zubairov Assigned To: Shigeru Chiba Priority: Blocker Attachments: exception.txt Original Estimate: 3 hours Remaining Estimate: 3 hours Classes that are generated using Javassist have no associated protection domain therefore it is not possible for JVM to assign permissions based on the static JAR files names, this is severe problem because it is not possible to grant permissions, hence all permissions are vorbidden, since that nothing works. Javassist is used by HiveMind to generate proxy classes for it's services, an see the stack trace (in attachment) the generated classes can't be associated with any ProtectionDomain, therefore _any Javassist supported application is impossble to start under strict security in Java_.

Renat Zubairov (JIRA)

5:44 p.m.

New subject: [JBoss JIRA] Commented: (JASSIST-23) Java 2 Security ProtiectionDomain is not associated with new generated classes

[ http://jira.jboss.com/jira/browse/JASSIST-23?page=comments#action_12340715 ] Renat Zubairov commented on JASSIST-23: --------------------------------------- Actually HiveMind is using convinience methods that are located inside CtClass class. I have fixed the problem already, and testted how it works, however the problem I don't know what will be the best solution for the problem, there is several alternatives: 1. Let the client decide which ProtectionDomain should be used during the classloading - make this decision mandatory for all clients 2. Let clients decide wherever they want to have a new classes associated with ProtectionDomain or not - potential securty problem 3. Associate all classes loaded by the Javassist with the Javassist protection domain I would prefer to declare old method as deprecated, and declare additional method with ProtectionDomain as parameter, then clients can decide which protection domain they want to use. P.S. As soon you will decide I can submit this fix either directly to SCV or as patch file and trigger changes in the Hivemind project

...

Java 2 Security ProtiectionDomain is not associated with new generated classes ------------------------------------------------------------------------------ Key: JASSIST-23 URL: http://jira.jboss.com/jira/browse/JASSIST-23 Project: Javassist Issue Type: Bug Environment: IBM WebSphere 5.1 with J2EE Security ON, Javassist 3.0, Tapestry 4.1, HiveMind 1.1.1 Reporter: Renat Zubairov Assigned To: Shigeru Chiba Priority: Blocker Attachments: exception.txt Original Estimate: 3 hours Remaining Estimate: 3 hours Classes that are generated using Javassist have no associated protection domain therefore it is not possible for JVM to assign permissions based on the static JAR files names, this is severe problem because it is not possible to grant permissions, hence all permissions are vorbidden, since that nothing works. Javassist is used by HiveMind to generate proxy classes for it's services, an see the stack trace (in attachment) the generated classes can't be associated with any ProtectionDomain, therefore _any Javassist supported application is impossble to start under strict security in Java_.

Shigeru Chiba (JIRA)

6:52 p.m.

New subject: [JBoss JIRA] Commented: (JASSIST-23) Java 2 Security ProtiectionDomain is not associated with new generated classes

[ http://jira.jboss.com/jira/browse/JASSIST-23?page=comments#action_12340720 ] Shigeru Chiba commented on JASSIST-23: -------------------------------------- For keeping compatibility, I would have to take the 2nd option. By the way, how do you fix a bug in Hivemind? Since Javassist has also a proxy generator library, it has the same problem on a sealed jar file. So I appreciate if you suggest a possible fix to me. Thanks

...

Java 2 Security ProtiectionDomain is not associated with new generated classes ------------------------------------------------------------------------------ Key: JASSIST-23 URL: http://jira.jboss.com/jira/browse/JASSIST-23 Project: Javassist Issue Type: Bug Environment: IBM WebSphere 5.1 with J2EE Security ON, Javassist 3.0, Tapestry 4.1, HiveMind 1.1.1 Reporter: Renat Zubairov Assigned To: Shigeru Chiba Priority: Blocker Attachments: exception.txt Original Estimate: 3 hours Remaining Estimate: 3 hours Classes that are generated using Javassist have no associated protection domain therefore it is not possible for JVM to assign permissions based on the static JAR files names, this is severe problem because it is not possible to grant permissions, hence all permissions are vorbidden, since that nothing works. Javassist is used by HiveMind to generate proxy classes for it's services, an see the stack trace (in attachment) the generated classes can't be associated with any ProtectionDomain, therefore _any Javassist supported application is impossble to start under strict security in Java_.

Renat Zubairov (JIRA)

9:18 p.m.

New subject: [JBoss JIRA] Commented: (JASSIST-23) Java 2 Security ProtiectionDomain is not associated with new generated classes

[ http://jira.jboss.com/jira/browse/JASSIST-23?page=comments#action_12340721 ] Renat Zubairov commented on JASSIST-23: --------------------------------------- I haven't fixed it yet in the HiveMind, the fix I've done so far to give it a try is just associating ProtectionDomain from Javassist classes with newly loaded classes, it just gave me oppotunity to associate loaded classes with something, but it is not a solution for the problem in general. Should I declare old method which is not safe as deprecated?

...

Java 2 Security ProtiectionDomain is not associated with new generated classes ------------------------------------------------------------------------------ Key: JASSIST-23 URL: http://jira.jboss.com/jira/browse/JASSIST-23 Project: Javassist Issue Type: Bug Environment: IBM WebSphere 5.1 with J2EE Security ON, Javassist 3.0, Tapestry 4.1, HiveMind 1.1.1 Reporter: Renat Zubairov Assigned To: Shigeru Chiba Priority: Blocker Attachments: exception.txt Original Estimate: 3 hours Remaining Estimate: 3 hours Classes that are generated using Javassist have no associated protection domain therefore it is not possible for JVM to assign permissions based on the static JAR files names, this is severe problem because it is not possible to grant permissions, hence all permissions are vorbidden, since that nothing works. Javassist is used by HiveMind to generate proxy classes for it's services, an see the stack trace (in attachment) the generated classes can't be associated with any ProtectionDomain, therefore _any Javassist supported application is impossble to start under strict security in Java_.

Shigeru Chiba (JIRA)

Monday, 7 August Mon, 7 Aug

4:12 a.m.

New subject: [JBoss JIRA] Commented: (JASSIST-23) Java 2 Security ProtiectionDomain is not associated with new generated classes

[ http://jira.jboss.com/jira/browse/JASSIST-23?page=comments#action_12340723 ] Shigeru Chiba commented on JASSIST-23: -------------------------------------- I am now working on this problem of Javassist. Since other JBoss projects depend on Javassist and they override toClass(), I have to discuss with other developers... Simple changes/fixes might be dangerous.

...

Java 2 Security ProtiectionDomain is not associated with new generated classes ------------------------------------------------------------------------------ Key: JASSIST-23 URL: http://jira.jboss.com/jira/browse/JASSIST-23 Project: Javassist Issue Type: Bug Environment: IBM WebSphere 5.1 with J2EE Security ON, Javassist 3.0, Tapestry 4.1, HiveMind 1.1.1 Reporter: Renat Zubairov Assigned To: Shigeru Chiba Priority: Blocker Attachments: exception.txt Original Estimate: 3 hours Remaining Estimate: 3 hours Classes that are generated using Javassist have no associated protection domain therefore it is not possible for JVM to assign permissions based on the static JAR files names, this is severe problem because it is not possible to grant permissions, hence all permissions are vorbidden, since that nothing works. Javassist is used by HiveMind to generate proxy classes for it's services, an see the stack trace (in attachment) the generated classes can't be associated with any ProtectionDomain, therefore _any Javassist supported application is impossble to start under strict security in Java_.

Renat Zubairov (JIRA)

8:52 a.m.

New subject: [JBoss JIRA] Updated: (JASSIST-23) Java 2 Security ProtiectionDomain is not associated with new generated classes

[ http://jira.jboss.com/jira/browse/JASSIST-23?page=all ] Renat Zubairov updated JASSIST-23: ---------------------------------- Attachment: ClassPool.java Fixed version of the ClassPool class.

...

Java 2 Security ProtiectionDomain is not associated with new generated classes ------------------------------------------------------------------------------ Key: JASSIST-23 URL: http://jira.jboss.com/jira/browse/JASSIST-23 Project: Javassist Issue Type: Bug Environment: IBM WebSphere 5.1 with J2EE Security ON, Javassist 3.0, Tapestry 4.1, HiveMind 1.1.1 Reporter: Renat Zubairov Assigned To: Shigeru Chiba Priority: Blocker Attachments: ClassPool.java, exception.txt Original Estimate: 3 hours Remaining Estimate: 3 hours Classes that are generated using Javassist have no associated protection domain therefore it is not possible for JVM to assign permissions based on the static JAR files names, this is severe problem because it is not possible to grant permissions, hence all permissions are vorbidden, since that nothing works. Javassist is used by HiveMind to generate proxy classes for it's services, an see the stack trace (in attachment) the generated classes can't be associated with any ProtectionDomain, therefore _any Javassist supported application is impossble to start under strict security in Java_.

Renat Zubairov (JIRA)

8:56 a.m.

New subject: [JBoss JIRA] Commented: (JASSIST-23) Java 2 Security ProtiectionDomain is not associated with new generated classes

[ http://jira.jboss.com/jira/browse/JASSIST-23?page=comments#action_12340731 ] Renat Zubairov commented on JASSIST-23: --------------------------------------- I'm in my office today, therefore that's a details of what I've found: 1. The problem causing method in my case is method public Class toClass(CtClass ct, ClassLoader loader) in the ClassPool class, I think it worth to create another method with similar signature but with protection domain as additional parameter.In the attachments you can find a fixed version of the ClassPool class with additional method public Class toClass(CtClass ct, ClassLoader loader, ProtectionDomain protectionDomain), I've updated the old method and javadoc to both of them. 2. Potentially unsafe methods are also used in following places: a. Loader class - in the method Class findClass(String name) - there class is loaded without ProtectionDomain association b. util.proxy.FactoryHelper in the method public static Class toClass(ClassFile cf, ClassLoader loader) - the same ussage as in ClassPool, I don't understand why there is similar method needed c. tools.web.Viewer in the method Class findClass(String name) - probably minor utility but still.

...

Java 2 Security ProtiectionDomain is not associated with new generated classes ------------------------------------------------------------------------------ Key: JASSIST-23 URL: http://jira.jboss.com/jira/browse/JASSIST-23 Project: Javassist Issue Type: Bug Environment: IBM WebSphere 5.1 with J2EE Security ON, Javassist 3.0, Tapestry 4.1, HiveMind 1.1.1 Reporter: Renat Zubairov Assigned To: Shigeru Chiba Priority: Blocker Attachments: ClassPool.java, exception.txt Original Estimate: 3 hours Remaining Estimate: 3 hours Classes that are generated using Javassist have no associated protection domain therefore it is not possible for JVM to assign permissions based on the static JAR files names, this is severe problem because it is not possible to grant permissions, hence all permissions are vorbidden, since that nothing works. Javassist is used by HiveMind to generate proxy classes for it's services, an see the stack trace (in attachment) the generated classes can't be associated with any ProtectionDomain, therefore _any Javassist supported application is impossble to start under strict security in Java_.

Shigeru Chiba (JIRA)

10:38 a.m.

New subject: [JBoss JIRA] Commented: (JASSIST-23) Java 2 Security ProtiectionDomain is not associated with new generated classes

[ http://jira.jboss.com/jira/browse/JASSIST-23?page=comments#action_12340734 ] Shigeru Chiba commented on JASSIST-23: -------------------------------------- This problem might be also due to the same bug: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=86335

...

Java 2 Security ProtiectionDomain is not associated with new generated classes ------------------------------------------------------------------------------ Key: JASSIST-23 URL: http://jira.jboss.com/jira/browse/JASSIST-23 Project: Javassist Issue Type: Bug Environment: IBM WebSphere 5.1 with J2EE Security ON, Javassist 3.0, Tapestry 4.1, HiveMind 1.1.1 Reporter: Renat Zubairov Assigned To: Shigeru Chiba Priority: Blocker Attachments: ClassPool.java, exception.txt Original Estimate: 3 hours Remaining Estimate: 3 hours Classes that are generated using Javassist have no associated protection domain therefore it is not possible for JVM to assign permissions based on the static JAR files names, this is severe problem because it is not possible to grant permissions, hence all permissions are vorbidden, since that nothing works. Javassist is used by HiveMind to generate proxy classes for it's services, an see the stack trace (in attachment) the generated classes can't be associated with any ProtectionDomain, therefore _any Javassist supported application is impossble to start under strict security in Java_.

Shigeru Chiba (JIRA)

6:02 p.m.

New subject: [JBoss JIRA] Resolved: (JASSIST-23) Java 2 Security ProtiectionDomain is not associated with new generated classes

[ http://jira.jboss.com/jira/browse/JASSIST-23?page=all ] Shigeru Chiba resolved JASSIST-23. ---------------------------------- Resolution: Done Several toClass() in CtClass, ClassPool, and FactoryHelper were modified to receive a Protection Domain.

...

Java 2 Security ProtiectionDomain is not associated with new generated classes ------------------------------------------------------------------------------ Key: JASSIST-23 URL: http://jira.jboss.com/jira/browse/JASSIST-23 Project: Javassist Issue Type: Bug Environment: IBM WebSphere 5.1 with J2EE Security ON, Javassist 3.0, Tapestry 4.1, HiveMind 1.1.1 Reporter: Renat Zubairov Assigned To: Shigeru Chiba Priority: Blocker Attachments: ClassPool.java, exception.txt Original Estimate: 3 hours Remaining Estimate: 3 hours Classes that are generated using Javassist have no associated protection domain therefore it is not possible for JVM to assign permissions based on the static JAR files names, this is severe problem because it is not possible to grant permissions, hence all permissions are vorbidden, since that nothing works. Javassist is used by HiveMind to generate proxy classes for it's services, an see the stack trace (in attachment) the generated classes can't be associated with any ProtectionDomain, therefore _any Javassist supported application is impossble to start under strict security in Java_.

Shigeru Chiba (JIRA)

Monday, 23 October Mon, 23 Oct

5:58 a.m.

New subject: [JBoss JIRA] Closed: (JASSIST-23) Java 2 Security ProtiectionDomain is not associated with new generated classes

[ http://jira.jboss.com/jira/browse/JASSIST-23?page=all ] Shigeru Chiba closed JASSIST-23. --------------------------------

...

Java 2 Security ProtiectionDomain is not associated with new generated classes ------------------------------------------------------------------------------ Key: JASSIST-23 URL: http://jira.jboss.com/jira/browse/JASSIST-23 Project: Javassist Issue Type: Bug Environment: IBM WebSphere 5.1 with J2EE Security ON, Javassist 3.0, Tapestry 4.1, HiveMind 1.1.1 Reporter: Renat Zubairov Assigned To: Shigeru Chiba Priority: Blocker Attachments: ClassPool.java, exception.txt Original Estimate: 3 hours Remaining Estimate: 3 hours Classes that are generated using Javassist have no associated protection domain therefore it is not possible for JVM to assign permissions based on the static JAR files names, this is severe problem because it is not possible to grant permissions, hence all permissions are vorbidden, since that nothing works. Javassist is used by HiveMind to generate proxy classes for it's services, an see the stack trace (in attachment) the generated classes can't be associated with any ProtectionDomain, therefore _any Javassist supported application is impossble to start under strict security in Java_.

kevin armano (JIRA)

Tuesday, 21 November Tue, 21 Nov

6:07 a.m.

New subject: [JBoss JIRA] Commented: (JASSIST-23) Java 2 Security ProtiectionDomain is not associated with new generated classes

...

Java 2 Security ProtiectionDomain is not associated with new generated classes ------------------------------------------------------------------------------ Key: JASSIST-23 URL: http://jira.jboss.com/jira/browse/JASSIST-23 Project: Javassist Issue Type: Bug Environment: IBM WebSphere 5.1 with J2EE Security ON, Javassist 3.0, Tapestry 4.1, HiveMind 1.1.1 Reporter: Renat Zubairov Assigned To: Shigeru Chiba Priority: Blocker Attachments: ClassPool.java, exception.txt Original Estimate: 3 hours Remaining Estimate: 3 hours Classes that are generated using Javassist have no associated protection domain therefore it is not possible for JVM to assign permissions based on the static JAR files names, this is severe problem because it is not possible to grant permissions, hence all permissions are vorbidden, since that nothing works. Javassist is used by HiveMind to generate proxy classes for it's services, an see the stack trace (in attachment) the generated classes can't be associated with any ProtectionDomain, therefore _any Javassist supported application is impossble to start under strict security in Java_.

Ryan Campbell (JIRA)

6:27 p.m.

New subject: [JBoss JIRA] Updated: (JASSIST-23) Java 2 Security ProtiectionDomain is not associated with new generated classes

[ http://jira.jboss.com/jira/browse/JASSIST-23?page=all ] Ryan Campbell updated JASSIST-23: --------------------------------- Comment: was deleted

...

Java 2 Security ProtiectionDomain is not associated with new generated classes ------------------------------------------------------------------------------ Key: JASSIST-23 URL: http://jira.jboss.com/jira/browse/JASSIST-23 Project: Javassist Issue Type: Bug Environment: IBM WebSphere 5.1 with J2EE Security ON, Javassist 3.0, Tapestry 4.1, HiveMind 1.1.1 Reporter: Renat Zubairov Assigned To: Shigeru Chiba Priority: Blocker Attachments: ClassPool.java, exception.txt Original Estimate: 3 hours Remaining Estimate: 3 hours Classes that are generated using Javassist have no associated protection domain therefore it is not possible for JVM to assign permissions based on the static JAR files names, this is severe problem because it is not possible to grant permissions, hence all permissions are vorbidden, since that nothing works. Javassist is used by HiveMind to generate proxy classes for it's services, an see the stack trace (in attachment) the generated classes can't be associated with any ProtectionDomain, therefore _any Javassist supported application is impossble to start under strict security in Java_.

6429

days inactive

6555

days old

jboss-jira@lists.jboss.org

Manage subscription

15 comments

4 participants

tags (0)

participants (4)

kevin armano (JIRA)
Renat Zubairov (JIRA)
Ryan Campbell (JIRA)
Shigeru Chiba (JIRA)

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

[JBoss JIRA] Created: (JASSIST-23) Java 2 Security ProtiectionDomain is not associated with new generated classes