On 8/31/05, Conrad Friedrich <[EMAIL PROTECTED]> wrote:
> Is there a way to prevent users (that got a client ssl-certificate (pkcs12)
> for accessing my server) from giving their certs away to others and in that
> way enabling "unwanted" users access to my site?
The client certificate acts as the
Hello,
Is there a way to prevent users (that got a client ssl-certificate (pkcs12)
for accessing my server) from giving their certs away to others and in that
way enabling "unwanted" users access to my site?
Or if there is no elegant solution, maybe someone knows how apache (or a log
analyzer et
Hello,
Is there a way to prevent users (that got a client ssl-certificate (pkcs12)
for accessing my server) from giving their certs away to others and in that
way enabling "unwanted" users access to my site?
Or if there is no elegant solution, maybe someone knows how apache (or a log
analyzer et
On Wed, Aug 31, 2005 at 10:47:39AM +0200, Bernhard Erdmann wrote:
> this is exactly what I recognized. When Apache 2.0.54 runs on RHEL AS 3
> using SSL, it opens TCP connections to itself on a regular schedule.
2.0 does this to wake up idle child processes, which can then exit, it's
perfectly no
Tom Henderson wrote:
Hi,
I hope that I describe my problem to the right mailinglist and that
someone can give me the hint I need.
I´m running a SuSE Linux 9.0 with Apache2 2.0.53 ( installed via rpm
from ftp.suse.com ) with mod_ssl. The startup parameter for the apache
is "-D SSL".
But here co