I have no idea why the security mechanism was changed. All I can tell
you is that I had the same problem with RMI stuff (on Solaris, even)
until I both gave all permissions to jre/lib/ext codebase AND created a
.java.policy file in my home directory which was identical to the
default java.policy file.
This could be a bug in the VM; on the other hand, this could also be the
intended functionality. I don't know for sure since I'm not involved in
the Java security development.
--Jeff
Chris Abbey wrote:
>
> At 21:59 12/18/99 -0700, Jeff Galyan wrote:
> >Actually, that makes sense. Java 2 has a different security structure
> >than previous releases. If you took away permissions from the jre libs,
> >then you'd get that error.
>
> That error makes sense to you because of security being restriced?
> HUH? in 1.1 that error had a single, clear, meaning. Why on earth
> would it make sense to overlap a completely different type of problem
> onto the same error? Why not a *security* error... or is this an
> attempt at security through obfuscation? -=Chris
>
> cabbey at home dot net <*> http://members.home.net/cabbey
> I want a binary interface to the brain!
> Today's opto-mechanical digital interfaces are just too slow!
>
> ----------------------------------------------------------------------
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
--
Jeff Galyan
http://www.anamorphic.com
http://www.sun.com
jeffrey dot galyan at sun dot com
talisman at anamorphic dot com
Sun Certified Java(TM) Programmer
======================================================================
Linus Torvalds on Microsoft and software development:
"... if it's a hobby for me and a job for you, why are you doing such a
shoddy job of it?"
The views expressed herein do not necessarily reflect those of my
employer.
Sun Microsystems, Inc., has no connection to my involvement with the
Mozilla Organization.
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]