# Re: sun.security.acl

Marianne Mueller (mrm@Eng)
Fri, 27 Jun 1997 09:49:43 -0700

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Vinod Anupam: "Re: Browser Vulnerability (VU#16403)"
- Previous message: Arjun Khanna: "sun.security.acl"
- Maybe in reply to: Arjun Khanna: "sun.security.acl"

    Date: Fri, 27 Jun 1997 09:49:43 -0700

    Message-Id: <199706271649.JAA16707@puffin.eng.sun.com>

    From: Marianne Mueller <mrm@Eng>

    To: arjun@chistech.com

    Subject: Re: sun.security.acl

The JDK 1.1 java.security.acl interfaces are used by the Java Web
Server (see http://jserv.javasoft.com for info about the server.)
Check that web site for info about how to get evaluation copies of
that software.

Starting with JDK 1.2 (public early access later this year, no firm
date announced), the base JDK will have integrated support for highly
configurable fine-grain access control. When I say "integrated", I
mean that the base JDK uses the same mechanisms to protect access to
resources like files and network connections that an application
programmer would use to add access control to his or her application.
This is different from an ACL package that isn't integrated with the
JDK's internal protection mechanisms.

As for java.security.Certificate, the interfaces have been
substantially cleaned up and upgraded for JDK 1.2, and support
X509v3. The previoux x509v1 implementation will remain where it is
(in sun.security) for backwards compatibility, but we would encourage
people to use the upgraded interfaces.

Sorry not have a firm date for you, but the good news is that we have
addressed both of your concerns in the JDK 1.2 release ...

Marianne

- Next message: Vinod Anupam: "Re: Browser Vulnerability (VU#16403)"
- Previous message: Arjun Khanna: "sun.security.acl"
- Maybe in reply to: Arjun Khanna: "sun.security.acl"