Closed Bug 220740 Opened 21 years ago Closed 21 years ago

cannot connect to banking apps, OCSP alert says response has date in future.

Categories

(Core :: Security, defect)

x86
OS/2
defect
Not set
major

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: jheifetz, Assigned: security-bugs)

References

()

Details

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

Note.  I saw a similar bug saying that there is a problem if the local clock is
off.  I reset my clock with NIST before entering this, so a clock discrepancy on
the client should not be the problem.

When connecting to any app that wants a userid and password (esp. on-line
banking), I get an pop-up alert

This problem is new with 1.5 RC1.
I have no problem with 1.3, 1.4, or even a 1.5 beta from August 28.

Reproducible: Always

Steps to Reproduce:
1.try to open web site (e.g. URL shown above)
2.
3.

Actual Results:  
pop up Alert showing error message "error trying validate certificate from ...
using OCSP - response contains a date which is in the future"

Expected Results:  
what it used to do - accept certificate and display the web page with the logon
prompt.
works for me in build 2003092805 (1.6a)  on Mac OS X 10.2.8
related: bug 216674 ?
I think Bugs 224443, 220740, 224593, & 188986 are duplicates.
*** Bug 224593 has been marked as a duplicate of this bug. ***
Other affected URLs from bug 224593:
www.shoprogers.com/web_auth/signin.asp
http://www.pcbanking.cibc.com/
www.cibc.ca    <= Click on "Sign On"
OS: other → OS/2
Jim & Walter: Have you guys installed the LIBC04FIX1 libraries
(http://download.innotek.de/gccos2/runtime/libc04fix1.zip)?  This was a fix for
the incorrect time in MailNews when using LIBC04.  Maybe you guys are seeing the
same thing.
I'm not Jim or Walter, but I did try your advice here with the 1.6 Alpha on OS/2
and it cures the problem.

A BLESSING UPON THEE, YOUNG MAN!

I guess we can't definitively close this one (and the others I noted above)
until 1.6 General Availability comes out.
I have now updated LIBC04.DLL as suggested by 
pedemont@us.ibm.com and the problem is gone.  I tested this 
with Mozilla 1.5 and Firebird 0.7 and it fixed both of 
them.  So I deduce that there was no bug in the actual 
Mozilla code after all.
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
> So I deduce that there was no bug in the actual 
> Mozilla code after all.

Nothing in Mozilla was broken or fixed.
Status: RESOLVED → UNCONFIRMED
Resolution: FIXED → ---
->WORKSFORME
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago21 years ago
Resolution: --- → WORKSFORME
*** Bug 224443 has been marked as a duplicate of this bug. ***
You need to log in before you can comment on or make changes to this bug.