From: "Clyde Kunst" <clyde@webobject.com>
To: <java-security@java.sun.com>
Subject: What a mess!
Date: Fri, 2 Jul 1999 07:26:59 -0700
What a mess signing and deploying java code is today. Write once, rewrite
everywhere.
Currently, there is Microsoft Authenticode for IE with cabinet files.
Netscape uses Jar files with Netscape signing. The Mac uses JDK 1.1.7 and
Sun signing using Jar files. There is Sun 1.1 signing and Sun 1.2 signing.
Sun 1.2 signing with the plugin sucks. You expect the user that just loaded
my applet over the web to do the following:
1)Get a copy of Duke's certificate and store it in a file named Duke.x509
2)% keytool -import -alias Duke -file Duke.x509
3) Download the policy file that will grant code signed by Duke and
downloaded from the Java Software website to write to your local filesystem.
Just so my applet can write a file on her machine. Did you plan to make Java
so unusable?
Here is what I want. On the Mac, running Java (MRJ) 2.1.2, I want to sign
an applet, have it show the certificate. This code wants access to you
local file system. Trust it, yes or no!
The question then:
How do I sign an applet(that wants local file access) on the Mac, running
MRJ 2.1.2 and deploy it over the internet?
This is your chance to save me from returning to the safety of the Microsoft
camp!
Clyde Kunst
Avalon Microsystems, Inc.
clyde@webobject.com
www.webobject.com