Bug 43755

Summary:	Add a SSLOptions to don't fill SSL_CLIENT_VERIFY
Product:	Apache httpd-2	Reporter:	Bruno Bonfils <asyd>
Component:	mod_ssl	Assignee:	Apache HTTPD Bugs Mailing List <bugs>
Status:	RESOLVED LATER
Severity:	enhancement	Keywords:	MassUpdate, PatchAvailable
Priority:	P2
Version:	2.2.6
Target Milestone:	---
Hardware:	All
OS:	All
Attachments:	NoClientVerifyEnvVars patch

Description Bruno Bonfils 2007-10-31 08:50:37 UTC

For a verify specific purpose (explained later), I need to define
SSL_CLIENT_VERIFY to SUCCESS by another module than mod_ssl even if there is no
X509 client certificate authentication. 

To achieve my whish, I wrote a small patch which add the NoClientVerifyEnvVars
options to SSLOptions, if this option is enabled, mod_ssl skip this variable.

The patch can be found here: http://kaoru.asyd.net/~asyd/ssl.patch

This patch can probably be useful for others usage, that's why I submit it..

Context: I actually work on a mod_perl module which use an extended CAS (Central
Authentication Services) - a SSO solution - to authenticate users, and provide a
fake SSL X509 client authentication from a certificate provided in the CAS
answer. To be sure that this module can work with out modify applications, I
want to set SSL_CLIENT_VERIFY to SUCCESS, but I'm not able to overwrite the
variable, that's why I wrote this patch.

Comment 1 Bruno Bonfils 2007-10-31 08:51:14 UTC

Created attachment 21071 [details]
NoClientVerifyEnvVars patch

Comment 2 William A. Rowe Jr. 2018-11-07 21:08:45 UTC

Please help us to refine our list of open and current defects; this is a mass update of old and inactive Bugzilla reports which reflect user error, already resolved defects, and still-existing defects in httpd.

As repeatedly announced, the Apache HTTP Server Project has discontinued all development and patch review of the 2.2.x series of releases. The final release 2.2.34 was published in July 2017, and no further evaluation of bug reports or security risks will be considered or published for 2.2.x releases. All reports older than 2.4.x have been updated to status RESOLVED/LATER; no further action is expected unless the report still applies to a current version of httpd.

If your report represented a question or confusion about how to use an httpd feature, an unexpected server behavior, problems building or installing httpd, or working with an external component (a third party module, browser etc.) we ask you to start by bringing your question to the User Support and Discussion mailing list, see [https://httpd.apache.org/lists.html#http-users] for details. Include a link to this Bugzilla report for completeness with your question.

If your report was clearly a defect in httpd or a feature request, we ask that you retest using a modern httpd release (2.4.33 or later) released in the past year. If it can be reproduced, please reopen this bug and change the Version field above to the httpd version you have reconfirmed with.

Your help in identifying defects or enhancements still applicable to the current httpd server software release is greatly appreciated.