This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 12326 - Security manager ignoring AllPermissions
Summary: Security manager ignoring AllPermissions
Status: RESOLVED INVALID
Alias: None
Product: obsolete
Classification: Unclassified
Component: jini (show other bugs)
Version: 3.x
Hardware: PC Linux
: P3 blocker (vote)
Assignee: issues@obsolete
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-05-22 08:39 UTC by mdm42
Modified: 2001-09-13 09:32 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
IDE Logfile showing exceptions. (8.59 KB, text/plain)
2001-07-20 20:45 UTC, mdm42
Details
IDE security policy. (1.12 KB, text/plain)
2001-07-20 20:45 UTC, mdm42
Details

Note You need to log in before you can comment on or make changes to this bug.
Description mdm42 2001-05-22 08:39:40 UTC
Working with Jini stuff, I have adjusted the ide.policy to enable relevant
permissions, but getting an exception (java.lang.RuntimePermission
modifyThreadGroup, needed by Jini's ServiceDiscoveryManager, among other
classes) when java.security.AllPermission has been granted to ALL relevant
codebases.  Will attach ide.log and ide.policy.
Comment 1 mdm42 2001-05-22 08:40:38 UTC
Created attachment 1398 [details]
IDE Logfile showing exceptions.
Comment 2 mdm42 2001-05-22 08:42:47 UTC
Created attachment 1399 [details]
IDE security policy.
Comment 3 anovak 2001-09-11 12:33:38 UTC
I am assigning this to JINI module as it seems that the problem is there.
Comment 4 anovak 2001-09-11 14:25:08 UTC
Reassigning.
Comment 5 _ pkuzel 2001-09-11 14:47:43 UTC
Strange, Mike is jini-ext.jar really at location that has granted
AllPermissions? It can be somewhere at class path.
Comment 6 Martin Ryzl 2001-09-11 15:39:27 UTC
Where are your jini-ext.jar and jini-core.jar located? Put them into 
either ${java.home}/lib/ext or ${netbeans.user}/lib/ext and everything 
should work well.
Comment 7 mdm42 2001-09-13 09:32:13 UTC
Well, its a long time ago now, and I have lost the original files in
the upgrade to NB3.2.1 (including the policy file I created to work
around the problem :->)

The jini jar files (jini-core, jini-ext and most likely sun-util as
well) were /very definitely/ in ${netbeans.home}/lib/ext as can be
seen in the ide.log file I attached to the original report.  Another
indication that the jarfiles were accessible is that all other Jini
method calls worked fine; it was only modifyThreadGroup permission
that failed.

However, as I have stupidly lost the policy file I created to work
around the problem, and cannot now reproduce the bug (I have not
checked cvs for any changes to the security manager), I am marking
this as RESOLVED/INVALID.

My apologies for any inconvenience.