Closed Bug 224593 Opened 21 years ago Closed 21 years ago

When I try to "sign in" on this or certain other commercial web sites, I get an error message stating "Error while trying to validate certificate from www.shoprogers.com using OCSP - response contains a date which is in the future."

Categories

(Core Graveyard :: Security: UI, defect)

Other Branch
x86
OS/2
defect
Not set
major

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 220740

People

(Reporter: walter.os2, Assigned: ssaux)

References

()

Details

User-Agent:       Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.5) Gecko/20031017
Build Identifier: Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.5) Gecko/20031017

I have frequently accessed this page successfully with Mozilla 1.4 and earlier
versions.

I get the same result with this the www.cibc.ca site when I click on "Sign On"
or go to http://www.pcbanking.cibc.com/ .

I have all three SSL protocols checked on the middle OCSP line under Validation
checked.
 

Reproducible: Always

Steps to Reproduce:
1.  Just go to either https://www.shoprogers.com/web-auth/signin.asp or
http://www.pcbanking.cibc.com
2.
3.

Actual Results:  
The message "Error while trying to validate certificate from www.shoprogers.com
using OCSP - response contains a date which is in the future." is displayed on
the screen and I cannot proceed.
not security sensitive
Assignee: security-bugs → ssaux
Group: security
Component: Security: General → Client Library
Product: Browser → PSM
QA Contact: bmartin
Version: Trunk → unspecified
Reporter:
Is you local system date correct ?
Can you set your clock 1 hour in the future and try it again ?
Can you check it with a windows Mozilla (if you have a win32 system availible)
OS: other → OS/2
I think Bugs 224443, 220740, 224593, & 188986 are duplicates.

*** This bug has been marked as a duplicate of 220740 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Product: PSM → Core
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.