Bug 53037 - clarify mod_ssl documentation on the UID/GID context under which PKI related files are loaded and whether they are reloaded periodically
Summary: clarify mod_ssl documentation on the UID/GID context under which PKI related ...
Status: NEW
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: Documentation (show other bugs)
Version: 2.5-HEAD
Hardware: All All
: P2 enhancement (vote)
Target Milestone: ---
Assignee: HTTP Server Documentation List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-04-05 11:25 UTC by Christoph Anton Mitterer
Modified: 2012-04-05 16:00 UTC (History)
0 users


Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Christoph Anton Mitterer 2012-04-05 11:25:31 UTC 
Hi.

This originates out of bug #52630...

May I suggest to clarify mod_ssl's documentation a bit:
As far as I understand,  Apache starts as user root and after some
initialisation suids to some other user (e.g. www-data or so).

I must assume, that mod_ssl already loads some of its files in the root-user
context, because all the host certificates/keys, i.e. the files specified by:
- SSLCertificateFile
- SSLCertificateKeyFile
- SSLCertificateChainFile
were then root owned (and root-only readable), too.

But apparently (which is why I had all the troubles above) this is different
for some/all of the files specified by:
- SSLCACertificateFile/Path
- SSLCADNRequestFile/Path
- SSLCARevocationFile/Path
and they are read as (e.g.) www-data.


So could you please add information to mod_ssl's documentation for ALL of the 9
directives mentioned above:
a) under which context the files are read (root or apache-user)
b) whether they are constantly re-read or not
This is not only important as the they suid has already happened "later" but
also in general, as these files may change and people want to know whether they
have to restart the server for changes to get noticed.


Cheers,
Chris.