# FYI: comp.lang.java.security

Jan-Henrik Haukeland (jh@nextel.no)
17 Jun 1999 15:36:41 +0200

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Serafin Jose Estevez Andres: "RuntimePermission "exitVM" / Threads permissions"
- Previous message: Thorsten Goeller: "Java Cryptography Architecture in JDK1 .2"

    To: java-security@java.sun.com

    Subject: FYI: comp.lang.java.security

    From: Jan-Henrik Haukeland <jh@nextel.no>

    Date: 17 Jun 1999 15:36:41 +0200

Serafin Jose Estevez Andres <i2883439@petra.euitio.uniovi.es> writes:

> Well, once installed the SecurityManager, since the permission
> RuntimePermission("exitVM") isn't specified in the policy file, a call to
> System.exit() should throw AccessControlException, but it doesn't.

I have the same problem (on Solaris jdk 1.2.2). I suspect it's a
(design) bug. This bug report may explain why it's so:

http://developer.java.sun.com/developer/bugParade/bugs/4052936.html

I just hope that it's not so, since it's much more elegant to use a
policy file instead of implementing a SecurityManager. And I really
must stop System.exit since we're hosting servlets, and we can't have
a customer issuing a System.exit from his servlet :-}

    --
    Jan-Henrik Haukeland

- Next message: Serafin Jose Estevez Andres: "RuntimePermission "exitVM" / Threads permissions"
- Previous message: Thorsten Goeller: "Java Cryptography Architecture in JDK1 .2"