> > This only works for the appletviewer, applications do not make
any
> > use of the java.policy file per default in the Linux 1.2 version.
> > You need to set a runtime option if you want to use it.
> > This will change in JDK 1.3
> >
>
> That is NOT TRUE. I was getting security exceptions when doing normal
> things like reading/writing from a file and connecting to the rmi
> registry. When I used the policy tool my problems went away.
Excerpt from the 1.3 release notes:
________________________________________________________
However, this means that in the Java 2 SDK, application classes
no longer have all permissions by default. Instead, they are
granted permissions based on the system's configured security
policy.
________________________________________________________
This has been invented with 1.3 and did not apply to versions <1.3
Though I am not sure about 1.2.2.
The Linux 1.2prev2 works fine without setting the policy (which
means that our proxy eg reads and writes files, opens connections,
etc.)
If you use the java -
Djava.security.policy=sun.security.provider.PolicyFileoption
then the default implementation applies.
Talking about Windows it must propably be a 1.3beta being used.
Oliver
___________________________________________________
Oliver Fels | e-mail:
IQena GmbH | [EMAIL PROTECTED]
Team Manager JAVA-/IT-Security | http://www.iqena.com
Friedrichshafen, Germany |
---------------------------------------------------
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
