Bug 48228 - Renegocation requires multiple client authentication on mod_autoindex listings
Summary: Renegocation requires multiple client authentication on mod_autoindex listings
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: mod_ssl (show other bugs)
Version: 2.2.13
Hardware: All All
: P2 normal (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
Keywords: MassUpdate
Depends on: 48215
  Show dependency tree
Reported: 2009-11-18 09:27 UTC by jmdesp
Modified: 2018-11-07 21:08 UTC (History)
0 users

The error log with LogLevel debug (329.70 KB, text/plain)
2009-11-18 09:27 UTC, jmdesp
debugging patch (741 bytes, patch)
2009-11-19 00:23 UTC, Joe Orton
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description jmdesp 2009-11-18 09:27:15 UTC
Created attachment 24558 [details]
The error log with LogLevel debug

After connecting to an URL without client authentication, connection to an URL
that requires it and lists the content of a directory using mod_autoindex,
start a SSL renegociation several times instead of only once.

Reloading that page starts the SSL renegociation again.

The reproduction procedure is almost the same as for bug 48215.
I changed SSLVerifyDepth location, and to use NULL encryption to make analyzing
the SSL traffic easier (despite having the key, tshark sometimes fails to

- edit the default httpd.conf and add/replace the following in the default
configuration :
Listen *:443

LoadModule ssl_module modules/mod_ssl.so
LoadModule autoindex_module modules/mod_autoindex.so

SSLSessionCache        "shmcb:${path}/apache/logs/ssl_scache(512000)"
SSLSessionCacheTimeout  3000
# Use this instead if you don't need the clear text traffic 
# SSLCipherSuite AES+RSA+SHA1

NameVirtualHost *:443
<VirtualHost *:443>
   SSLEngine On 
   SSLCertificateFile "${path}/apache/conf/authentication.cer"
   SSLCertificateKeyFile "${path}/apache/conf/authentication.key"
   SSLVerifyDepth 0
   <Location /authentication/>
    SSLVerifyClient optional_no_ca
   DocumentRoot "${path}/www"
- create a index.html file in /www
    <html><head><title> authentication test </title></head>
    <body>authentication test<hr>
    <a href="/authentication" >authentication link</a>
- create /www/authentication
- create 10 files inside authentication 1.html through 10.html, the content of
the files is not important
- If you have the NULL cipher suite configured :
    Inside firefox, in about:config, set security.ssl3.rsa_null_sha to true
(you'll need to set this value to false again later for security)
- connect firefox to /
- follow the link on the page to /authentication
- You'll need a client certificate (a sample p12 is included in the repro
- Have the "remember certificate" option unchecked
- Apache will immediately request authentication a second time
- Reload the page with the reload button 
- Apache will request authentication again two times in a row (in bug 48215,
reloading the page does not cause the same problem)

The big plus of NULL encryption is that with it (BIO dump follows) in error_log
shows all the HTTP traffic in the clear.
Comment 1 jmdesp 2009-11-18 09:35:44 UTC
Comment on attachment 24558 [details]
The error log with LogLevel debug

As NULL encryption is used, all the request from the client can be seen
Comment 2 Joe Orton 2009-11-19 00:23:35 UTC
Created attachment 24563 [details]
debugging patch

Part of this is probably bug 47055.

I'm not sure why the initial renegotiation is forced, though - it's for a subrequest but it isn't obvious why.

Can you rebuild with this patch applied to mod_ssl, and attach the new error_log produced?
Comment 3 William A. Rowe Jr. 2018-11-07 21:08:37 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.