| Summary: | ERROR: Verify that certificates have not been revoked with "mod_ssl" against "ocspd". | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Account closed by the user <b38617> | ||||
| Component: | httpd | Assignee: | Jan Kaluža <jkaluza> | ||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 19 | CC: | b38617, jkaluza, jorton, joseluis.gms, pahan | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2015-02-17 19:30:49 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
|
Description
Account closed by the user
2013-12-03 17:06:54 UTC
What failure is mod_ssl reporting? If the error is not obvious at the default loglevel try adding: LogLevel ssl:trace2 to the SSL vhost. Hi Joe: 'httpd' fails when it tries to verify that client certificates have been revoked or not with "mod_ssl" against "ocspd". With similar configuration in 'mod_nss' it works. We send the trace you requested for mod_ssl. Thanks. Jose Luis & Xose Created attachment 833294 [details]
http ocsp error
This: [Thu Dec 05 18:52:25.586811 2013] [ssl:error] [pid 574] AH01925: failed to verify the OCSP response [Thu Dec 05 18:52:25.586862 2013] [ssl:error] [pid 574] SSL Library Error: error:27069070:OCSP routines:OCSP_basic_verify:root ca not trusted [Thu Dec 05 18:52:25.586940 2013] [ssl:info] [pid 574] [client 192.168.58.1:38907] AH02276: Certificate Verification: Error (50): application verification failure [subject: CN=Bichos Network CA,OU=Bichos Network CA,O=Bichos,C=ES / issuer: CN=Bichos Root CA,OU=Bichos Root CA,O=Bichos,C=ES / serial: 01 / notbefore: Dec 4 16:57:59 2013 GMT / notafter: Dec 30 16:57:59 2029 GMT] ... says that you are not trusting that "Bichos Root CA" trusted in the mod_ssl configuration. (In reply to Joe Orton from comment #4) > This: > > [Thu Dec 05 18:52:25.586811 2013] [ssl:error] [pid 574] AH01925: failed to > verify the OCSP response > [Thu Dec 05 18:52:25.586862 2013] [ssl:error] [pid 574] SSL Library Error: > error:27069070:OCSP routines:OCSP_basic_verify:root ca not trusted > [Thu Dec 05 18:52:25.586940 2013] [ssl:info] [pid 574] [client > 192.168.58.1:38907] AH02276: Certificate Verification: Error (50): > application verification failure [subject: CN=Bichos Network CA,OU=Bichos > Network CA,O=Bichos,C=ES / issuer: CN=Bichos Root CA,OU=Bichos Root > CA,O=Bichos,C=ES / serial: 01 / notbefore: Dec 4 16:57:59 2013 GMT / > notafter: Dec 30 16:57:59 2029 GMT] > > ... says that you are not trusting that "Bichos Root CA" trusted in the > mod_ssl configuration. Hi, in this example 'Bichos CA' is trusted in the mod_ssl configuration and with https requests (ssl normal operation) it works, no errors shown for certificates from 'Bichos CA'. The question is why operating with OCSP results in that certificate verification error. Best regards. José Luis This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |