On Oct 4, 2009, at 11:01 PM, Peter Firmstone wrote:
Peter Jones wrote:
On Oct 4, 2009, at 3:42 AM, [email protected] wrote:
[snip]
In order for these files to get proper AllPermission for full
access these jar files will need to be signed in the build
process, since they are no longer being accessed from the jre/lib/
ext/ directory.
Jonathan could you set up the signing certificates for me please?
I don't understand this-- the AllPermission grants are just to a
code source, not limited to any particular signers, so they
shouldn't need to be signed.
Me either see below, I originally granted AllPermission to the
JTlib-tmp directory, but later changed it when I got the no signer
certificates errors.
The tests pass (except the usual 6 known failures) on this machine
when the jar files are in the jre/lib/ext/ directory
Note if you've got the latest build, you'll have to edit the
build.xml file to turn on the security debug option.
Note the jtreg -cpa: option in Ant doesn't seem to accept directory
classpaths JTlib-tmp/* for jar files, you have to list each jar file
separately.
[snip]
access: domain that failed ProtectionDomain (file:/opt/src/
ApacheRiver/trunk/qa/jtreg/JTlib-tmp/jsk-platform.jar <no signer
certificates>)
Note that this "no signer certificates" bit is just informational
about the JAR file-- it is not claiming the root cause of the problem.
sun.misc.launcher$appclassloa...@169e11
<no principals>
java.security.permissi...@137c60d (
(java.util.PropertyPermission * read,write)
(java.io.FilePermission /opt/src/ApacheRiver/trunk/qa/jtreg/JTwork/
classes/com/sun/jini/tool/CheckConfigurationFile/- write)
(java.io.FilePermission <<ALL FILES>> read)
(java.io.FilePermission /opt/src/ApacheRiver/trunk/qa/jtreg/JTwork/
classes/- read)
(java.io.FilePermission /opt/src/ApacheRiver/trunk/qa/jtreg/JTlib-
tmp/jsk-platform.jar read)
(java.lang.RuntimePermission *)
(java.lang.RuntimePermission exitVM)
)
Evidently the AllPermission grant isn't getting applied to jsk-
platform.jar in this case-- can you provide the exact test policy file
that was in use with this failure?
-- Peter
