Once I realised our problems were caused by not using the
default configuration in /conf/httpd.conf-dist,
it was plain sailing. We now have a working secure Apache!
A word of caution to others who, like me, attempt to add
mod_ssl to an existing configuration.
** Apache will preserve your
Ralf S. Engelschall wrote:
> Fred Read Wrote:
> > ...
> > I feel I am *almost* there but just need a tiny nudge in the
> > right direction.
Sorry for not responding sooner but I was taken ill on Friday
and have only just got your extremely valuable response.
> First, _please_ always start with
On Fri, 07 May 1999, Ted Rolle wrote:
>> situation. The problem is that for OpenSSL's parsing routines there seems to
>> be no difference between "not found" and "not decryptable" here and this way
>> mod_ssl can't give a more reasonable error message. I'll try to find a
>> solution for a better
On Fri, May 07, 1999, Ted Rolle wrote:
> > situation. The problem is that for OpenSSL's parsing routines there seems to
> > be no difference between "not found" and "not decryptable" here and this way
> > mod_ssl can't give a more reasonable error message. I'll try to find a
> > solution for a b
> situation. The problem is that for OpenSSL's parsing routines there seems to
> be no difference between "not found" and "not decryptable" here and this way
> mod_ssl can't give a more reasonable error message. I'll try to find a
> solution for a better error message...
Sounds like we need a fi
On Fri, May 07, 1999, Fred Read wrote:
> Boyce, Nick wrote:
> > Are you sure you've modified the server config to cause it to
> > expect SSL connections (as well as built it to be capable of them)?
> [...]
>
> SSLEngine on
> SSLCertificateFile /usr/local/apache/conf/ssl.crt/server.crt
>
Boyce, Nick wrote:
>
> Are you sure you've modified the server config to cause it to
> expect SSL connections (as well as built it to be capable of them)?
Thanks, that was it.
I added:
SSLLog /tmp/SSLLog
SSLLogLevel debug
SSLEngine on
SSLCertificateFile /usr/local/apache/conf/ssl.cr
> Fred Read writes:
Fred> We can access non secure web pages as "http://server/" and
Fred> "http://server/~user" but "https://server/" fails with the
Fred> following error message:
Fred> Netscape's network connection was refused by the server:
Fred>
Fred> The server may not be ac
> We can access non secure web pages as "http://server/" and
> "http://server/~user" but "https://server/" fails with the
> following error message:
>
> Netscape's network connection was refused by the server:
>
> The server may not be accepting connections or
> may be busy.
>
> Tr
Having written an authentication module for Apache which has
passed our testing and appears to be working fine we rebuilt
Apache with mod_ssl.
We can access non secure web pages as "http://server/" and
"http://server/~user" but "https://server/" fails with the
following error message:
Nets
10 matches
Mail list logo
