User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4a) Gecko/20030305 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4a) Gecko/20030305 Enabling OCSP functionality doesn't become effective immediately but requires a restart. Reproducible: Always Steps to Reproduce: 1. rm -rf $HOME/.mozilla 2. mozilla 3. import TLS site CA certificate, trust it 4. import OCSP responder's signing certificate, issued by previous CA certificate 5. Enable OCSP using the signer certificate imported in step 4 6. use the TLS site doesn't result in OCSP request 7. restart Mozilla 8. use the TLS site does result in OCSP request, which fails to error code -8174 Actual Results: . Expected Results: OCSP configuration should have been effective without a restart.
Don't mind about the "which fails to error code -8174" part in step eight, this was becaue of a malformed OCSP response. Otherwise the restart problem is still effective.
I can not confirm what you are reporting. - I started Mozilla with OCSP disabled - I connected to some SSL site - I configured Mozilla to always do OCSP with ocsp.verisign.com - I start tcpdump host ocsp.verisign.com - I connected to https://www.amazon.com - tcpdump showed matching OCSP packets I did not test the other configuration you suggested, which requires a site with a OCSP cert. Jyrki, which web server are you connecting to?
I'm using Debian packaged Mozilla 1.2.1, the site I'm connecting to is Tomcat 4. 0. rm -rf $HOME/.mozilla 1. start Mozilla 2. import our test CA certificate 3. import OCSP server's certificate which is issued by our test CA 4. select 'Use OCSP for cert. validation' - entering our own OCSP server 5. connect to SSL server which has revoked cert. 6. no OCSP query - confirmed with Ethereal 7. exit Mozilla 8. start Mozilla 9. connect to SSL server which has revoked cert. 10. OCSP query - confirmed with Ethereal - results a revoked response The only difference I see, is that I removed Mozilla settings before starting this experiment.
Jyrki, what I mean is: Can you please give us http://... addresses for your cert and site so we can test using it?
Mass reassign ssaux bugs to nobody
Assignee: ssaux → nobody
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.