# Minor problem with signed applet example with JDK114

Michael Seifert (seifert@flash.net)
Mon, 9 Feb 1998 23:30:32 -0600

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Li Gong: "Re: warning: applet window"
- Previous message: John Roach: "warning: applet window"

    From: "Michael Seifert" <seifert@flash.net>

    To: <java-security@web1.javasoft.com>

    Subject: Minor problem with signed applet example with JDK114

    Date: Mon, 9 Feb 1998 23:30:32 -0600

This is a multi-part message in MIME format.

------=_NextPart_000_007B_01BD35B2.B6E120A0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Dear sir or madam:

Sorry for bothering you- I am a student at the University of Texas at =
Arlington=20
currently writing my thesis on the benefits of JAVA in scientific =
programming.
I was recently investigating the security features in JDK 1.14, and ran =
across
the signed applet example ("Duke").

I successfully read the digital signature Duke.x509 and ran the signed =
applet
on both a Windows 95 machine (at home) and a Windows NT 4.0 machine (at =
work).

However, when I tried to duplicate the steps involved in creating a =
digital signature
and signing the applet, I was not able to get the Windows NT 4.0 machine =
to write
to my local disk (a security exception was thrown). I had no problems =
doing this
on my win95 machine at home. =20

Are there any peculiarities between the Windows 95 and NT 4.0 =
implementations?
Has the example been successfully tested under both operating systems? =
I am using
JDK 1.14 on both machines, and the class path is correctly defined on =
both machines.

I dont understand why I have no problem with Sun;s Duke.x509 file, but =
when I try
my Duke.x509 (which I created and tested successfully on my win95 =
machine) on
the NT 4.0 machine, the example continues to throw a security exception.

Any advice would be greatly appreciated. I'm using the doit script =
provided in the
example, and understand the basic javakey and jar requirements.

Thanks you,
mike=20

------=_NextPart_000_007B_01BD35B2.B6E120A0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
Dear sir or madam:
Sorry for bothering you- I am = a student at=20 the University of Texas at Arlington
currently writing my thesis on the = benefits of=20 JAVA in scientific programming.
I was recently investigating the = security=20 features in JDK 1.14, and ran across
the signed applet example=20 ("Duke").
I successfully read the digital signature Duke.x509 = and ran=20 the signed applet
on both a Windows 95 machine (at home) and a Windows = NT 4.0=20 machine (at work).
However, when I tried to duplicate the steps = involved in=20 creating a digital signature
and signing the applet, I was not able to get the = Windows NT=20 4.0 machine to write
to my local disk (a security exception was = thrown). I=20 had no problems doing this
on my win95 machine at home.
Are there any peculiarities between the Windows 95 = and NT 4.0=20 implementations?
Has the example been successfully tested under both = operating=20 systems? I am using
JDK 1.14 on both machines, and the class path is = correctly=20 defined on both machines.
I dont understand why I have no problem with Sun;s = Duke.x509=20 file, but when I try
my Duke.x509 (which I created and tested = successfully on my=20 win95 machine) on
the NT 4.0 machine, the example continues to throw a = security=20 exception.
Any advice would be greatly appreciated. I'm = using the=20 doit script provided in the
example, and understand the basic javakey and jar=20 requirements.
Thanks you,
mike
------=_NextPart_000_007B_01BD35B2.B6E120A0--

- Next message: Li Gong: "Re: warning: applet window"
- Previous message: John Roach: "warning: applet window"