Closed
Bug 139055
Opened 24 years ago
Closed 23 years ago
Added certificates not being used by Java plugin
Categories
(Core Graveyard :: Java-Implemented Plugins, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: stu, Assigned: blackconnect)
Details
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.9) Gecko/20020311
BuildID: 2002031104
It should be possible to add a certificate to Mozilla (by loading a .crt file,
for example) and then run Java applets signed with that certificate. While the
certificate is clearly accepted (it appears in Edit | Preferences | Privacy &
Security | Certificates), the Java plugin still treats applets signed with this
certificate as untrusted.
http://developer.java.sun.com/developer/qow/archive/99/index.html does a bad job
of explaining this process, but it should work. It does work under MSIE.
Reproducible: Always
Steps to Reproduce:
1. Create a Java applet, compile it, create a .jar file
2. Add a certificate using keytool (Sun utility) to a certificate store
3. Export that certificate (again using keytool) to a .crt file
4. Sign the jar file (using jarsigner) with the certificate
5. Add that .crt file to Mozilla's set of certificates (File | Open File will do
the trick); give that certificate the full set of rights
6. Write an html page with the applet/jar on it
7. Run that html page
Actual Results: A Java Plugin error message (it's got the metal look and feel)
pops up and says "java.security.cert.CertificateException : Unable to verify the
certificate with root CA"
Expected Results: Instead, Mozilla should either run the applet, or it should
pop a dialog asking me if I want to accept the certificate, etc.
This didn't used to be a problem; with JVMs before 1.3.1 the JVM would pop a
dialog saying that it was an untrusted certificate, and to ask what should be
done. This was still a bug (because it was already a trusted cert), just not a
killer. The user could choose the option to trust it.
Comment 1•23 years ago
|
||
"Reporter: Can you reproduce this bug with a recent build of Mozilla (for
example, 1.4 RC1)? If so, then please comment again with details. If not, then
please resolve this bug as WORKSFORME. Thanks."
URL: http://no particular URL
| Reporter | ||
Comment 2•23 years ago
|
||
Works with more recent versions of Mozilla. Excellent, thanks!
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
Updated•14 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•