The years in certificate validity encoded in GeneralizedTime are displayed in two-digit format

RESOLVED INVALID

Status

Core Graveyard
Security: UI
RESOLVED INVALID
14 years ago
a year ago

People

(Reporter: Wan-Teh Chang, Assigned: John G. Myers)

Tracking

Other Branch
x86
Windows 2000

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(4 attachments)

(Reporter)

Description

14 years ago
This bug was first mentioned in bug 229565 comment 3.

NSS 3.9 or newer supports GeneralizedTime.  However,
PSM displays the years in certificate validity
encoded in GeneralizedTime with only two digits.

Obviously the year in a GeneralizedTime should be
displayed with four digits.  I propose that we also
display the year in a UTCTime with four digits.
(Reporter)

Comment 1

14 years ago
Made the bug's summary clearer.
Summary: PSM displays the years in certificate validity encoded in GeneralizedTime with only two digits → The years in certificate validity encoded in GeneralizedTime are displayed in two-digit format
(Assignee)

Comment 2

14 years ago
Could someone please attach a test case?
John,  such a cert is attached to bug 212945.  
Question for c++@vip.at (who submitted bug 229565, from which this bug derived):

WHERE does the date display with a 2-digit year?
Please attach a screen shot.

I imported the cert attached to bug 212945, and examined it with the cert viewer.
The date was always shown with 4 digits, in both the General and Details tabs.
I couldn't find a cert date display that showed fewer than 4 digits.  

I tested on Win2k.  I have set my Win2K preference for date display in the 
Win2k "Regional Options" control panel (date tab) to yyyy-MM-dd and I see 
that format everywhere.   What date format have you selected?  
Perhaps this is a Windows issue rather than a moz issue??

Comment 5

14 years ago
Created attachment 138942 [details]
screenshot from linux build 2004010408

screenshot while trying to examine the cert under linux

Comment 6

14 years ago
Created attachment 138943 [details]
the root cert for tests

this is the root-cert i used for testing.

Comment 7

14 years ago
Created attachment 138944 [details]
screenshot from a windows client examining the cert

this is the info you'll see when you open the cert under windows

Comment 8

14 years ago
Created attachment 138945 [details]
output from openssl

and finally the result from an
[bash] openssl x509 -inform DER -in bp-root.cer -text -out erg.txt
(Assignee)

Comment 9

14 years ago
The date format is entirely controlled by the OS-level locale settings.  In Mac
OS X, changing the os-level locale preferences to include centuries in years
caused Mozilla to start displaying 4-digit years in the cert viewer.

The only alternative is to use an ISO8601-style date format (YYYY-MM-DD),
regardless of locale.
Status: NEW → RESOLVED
Last Resolved: 14 years ago
Resolution: --- → INVALID

Comment 10

14 years ago
i believe that showing the full year-format is the best option. the 
locale-settings should only drive the ordering and decoration of the date-format 
(YYYY-MM-DD or MM/DD/YYYY etc.)
(Assignee)

Comment 11

14 years ago
The choices are for the locale to completely handle the date format like it does
now or for the locale to have absolutely no effect on the date format.  There is
no middle ground.

Didn't mean to close this bug.
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
John, Agree with with your action in comment 9.  
Honor the user's locale choice.  Resolve invalid.
(Assignee)

Comment 13

14 years ago
Kai, it's your call.
(Assignee)

Updated

14 years ago
Assignee: kaie → jgmyers
Status: REOPENED → NEW

Comment 14

14 years ago
I fully agree.
On my Linux system with default locale setting I do see the full century.

Resolving invalid.
Status: NEW → RESOLVED
Last Resolved: 14 years ago14 years ago
Resolution: --- → INVALID

Updated

13 years ago
Component: Security: UI → Security: UI
Product: PSM → Core
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.