You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bugs@httpd.apache.org by bu...@apache.org on 2009/02/26 15:56:50 UTC

DO NOT REPLY [Bug 46773] New: SSLClientVerify directive not processed in documented directory order

https://issues.apache.org/bugzilla/show_bug.cgi?id=46773

           Summary: SSLClientVerify directive not processed in documented
                    directory order
           Product: Apache httpd-2
           Version: 2.2.11
          Platform: Sun
        OS/Version: Solaris
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Runtime Config
        AssignedTo: bugs@httpd.apache.org
        ReportedBy: dan.cushing@netideasinc.com


The configuration directives for Directory containers are supposed to be
processed in order of shortest to longest, to allow a general configuration to
be overridden by more specific subdirectory directives.  In the configuration
below I have specified 'SSLClientVerify require' globally.  In the registration
directory, where we cannot yet have it protected, I have specified
'SSLClientVerify none'.  I expected that to override the higher level directive
and allow this subdirectory to be accessed without a client certificate. 
Instead, it still requires a certificate to be presented.

<Directory "/webapp/root">
  Options None
  AllowOverride None
  Order Allow,Deny
  Allow from all
  SSLVerifyClient require
  SSLVerifyDepth 5
  AuthName "Web App Name"
  AuthType Basic
  AuthBasicProvider ldap
  AuthLDAPURL ldap://127.0.0.1/o=netideasinc.com?uid?one
  Require ldap-group cn=RegisteredUsers,ou=Groups,o=netideasinc.com
</Directory>

<Directory /webapp/root/registration">
  Options None
  Order Allow,Deny
  Allow from all
  SSLVerifyClient none
  AuthName "Web App Name"
  AuthType Basic
  AuthBasicProvider ldap
  AuthLDAPURL ldap://127.0.0.1/o=netideasinc.com?uid?one
  Require ldap-group cn=RegisteredUsers,ou=Groups,o=netideasinc.com
</Directory>

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


DO NOT REPLY [Bug 46773] SSLClientVerify directive not processed in documented directory order

Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=46773





--- Comment #4 from dan.cushing@netideasinc.com  2009-02-26 10:44:02 PST ---
Thanks for your time.  I thought I had pinned it down as a bug.  I'll hit the
users group and see if anybody knows the answer.

Appreciate the feedback from Will.  The odd thing is that I'm hitting the
<Directory "/webapp/root/registration"> location first, so the negotiation
should not include any client certificate requirements.  I added OptRenegotiate
and it doesn't help.

Odd thing is that I curiously tried it with Firefox and it works perfectly. 
IE7 is not working correctly.  Strange to me that this is browser dependent.

Just figured I'd post this to you to close things out.

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


DO NOT REPLY [Bug 46773] SSLClientVerify directive not processed in documented directory order

Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=46773





--- Comment #2 from dan.cushing@netideasinc.com  2009-02-26 07:45:02 PST ---
Just to be clear here, I do not have 'SSLClientVerify require' set at the
virtual host level.  I would have expected that to cause a problem.  It is only
set at the directory level.  In this case I expected it to work.  If you still
believe that this in an unsupported configuration I'll accept that and start
looking for a workaround, but I did want to make certain we had a common
understanding of the configuration.

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


DO NOT REPLY [Bug 46773] SSLClientVerify directive not processed in documented directory order

Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=46773





--- Comment #3 from Will Rowe <wr...@apache.org>  2009-02-26 07:52:55 PST ---
See OptRenegotiate under

http://httpd.apache.org/docs/2.2/mod/mod_ssl.html#ssloptions

It was a misconfiguration, but it is possible, contrary to Rudiger's comment,
to trigger the renegotiation only for specific accesses.  Note that this may
have a negative impact on large POST requests since the entire request body
must be cached first, and that's limited in terms of the bytes to set aside.

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


DO NOT REPLY [Bug 46773] SSLClientVerify directive not processed in documented directory order

Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=46773


Ruediger Pluem <rp...@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID




--- Comment #1 from Ruediger Pluem <rp...@apache.org>  2009-02-26 07:10:15 PST ---
Your approach cannot work from a logical point of view. If you require client
certificates on a global (virtualhost level) then the client certificate needs
to be checked before httpd is supplied with the URL which it enables it to know
that a check is not needed here. It is a chicken and egg problem.

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org