Wrong century reported for digital certificate for Java applet

RESOLVED INCOMPLETE

Status

Core Graveyard
Java: OJI
--
minor
RESOLVED INCOMPLETE
16 years ago
5 years ago

People

(Reporter: mozilla, Assigned: Kyle Yuan)

Tracking

Trunk
PowerPC
Mac OS X

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

16 years ago
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows 98)(Macintosh OS X bug 
reported from a Windows computer)
BuildID:    20011022

The Java applet at http://segal.org/SigningTest2055/index.html is signed using 
Sun's JDK 1.1 javakey signing system and a certificate that expires in 2055.  
The certificate actually works in Netscape/Mozilla for OS 10.1, but the browser 
reports the wrong century if you examine the certificate.   This works 
correctly in Netscape / Mozilla for OS 9.  This does not work using Windows 
browsers because those browsers use different signing systems.  

Reproducible: Always
Steps to Reproduce:
1. Java is enabled in Netscape 6.2 for OS 10.1 using the beta version 1.0d3 of 
the Mozilla OS X Java Plugin that was obtained from: 
http://homepage.mac.com/pcbeard/MRJPluginCarbon-1.0d3.sit; the MRJPlugin.jar 
and MRJPluginCarbon files were put in the /Library/Internet Plug-Ins folder.  

2.Compile the Java code below or run it at 
http://segal.org/SigningTest2055/index.html

3. When you get the "Java Security Alert" press "More Info" then "Expiration 
Date".


Actual Results:  1955

Expected Results:  2055

Java source code:
import java.awt.*;
import java.applet.*;

public class SigningTest extends Applet {

public void init() {}

public void paint(Graphics g)
{
    try
    {
        String userHome = System.getProperty("user.home");
        g.drawString("Signing worked. The user.home property is: " + userHome, 
10, 30);
    }
    catch (SecurityException e)
    {
    g.drawString("Signing didn't work. The SecurityException is: " + 
e.getMessage(), 10, 10);
    } 
}
} // END OF Class SigningTest

Comment 1

16 years ago
This bug was reported against Netscape 6.2 and so must be moved to Bugscape.

Reporter, if you wish to keep this bug in Bugzilla, you must confirm it against
a Mozilla, rather than Netscape build. If you do, reopen this bug.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → INVALID

Updated

16 years ago
Whiteboard: Move to Bugscape

Comment 2

16 years ago
Wait a sec, this doesn't need to be moved to Bugscape! Patrick is still working
on the OS X Java plugin.
Status: RESOLVED → UNCONFIRMED
Resolution: INVALID → ---
Whiteboard: Move to Bugscape

Comment 3

16 years ago
This will certainly happen in Mozilla as well. This is also certainly an Apple
Java VM bug. It looks like a type of Y2K problem. I know of no workaround.
Status: UNCONFIRMED → NEW
Ever confirmed: true

Comment 4

16 years ago
Marking WONTFIX, rather than INVALID, because it is something we can't work
around, you see Apple's code puts up those dialogs.
Status: NEW → RESOLVED
Last Resolved: 16 years ago16 years ago
Resolution: --- → WONTFIX
(Reporter)

Comment 5

16 years ago
I reported this to Apple but they claim this is a browser bug 
(http://segal.org/SigningTest2055/index.html).  However, since this occurs in 
both Internet Explorer and Netscape/Mozilla I agree this looks like an Apple 
problem.  I added to the bug report to Apple this argument for this being an 
Apple bug.
I get 1955 if I run the test case using the JDK1.3.1_02 Java Plug-in in 
Microsoft Internet Explorer 5 on Windows2000. This is not a Macintosh Java 
issue - this is a Sun Java issue.
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---

Updated

16 years ago
Status: REOPENED → ASSIGNED

Updated

15 years ago
QA Contact: pmac → petersen

Comment 7

11 years ago
-> default assignee for old netscape assigned bugs.
Assignee: beard → yuanyi21
Status: ASSIGNED → NEW
QA Contact: chrispetersen → zhayupeng

Updated

7 years ago
Component: Java: OJI → Java: OJI
Product: Core → Core Graveyard

Comment 8

5 years ago
Mass-closing bugs in the "OJI" component: OJI plugin integration was replaced with npruntime long ago, and these bugs appear to be irrelevant now. If there is in fact a real bug that remains, please file it new in the "Core" product, component "Plug-ins".
Status: NEW → RESOLVED
Last Resolved: 16 years ago5 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.