Ralf S. Engelschall wrote:
No, when the above two commands didn't complain the server.crt and server.key
are at least in correct format. Then, as you already mentioned yourself in
another reply, you should check the file permissions. Perhaps the files are
not readable for the user who
On Wed, Jan 20, 1999, Magnus Stenman wrote:
It would be nice if httpd would check
its name when starting up -- if its
httpsd, define SSL, otherwise don't
Then you only have to create a
symlink to httpd named httpsd
to choose which type of server to run
instead of the "ugly" -DSSL
The
On Wed, Jan 20, 1999, [EMAIL PROTECTED] wrote:
Full_Name:
Version: 2.1.7-1.3.4
OS: AIX 4.2 / apache 1.3.4
Submission from: felix.adpcl.com (194.98.137.100)
Error when compiling src/modules/ssl/mod_ssl.c
"ssl_expr.h", line 103.51: 1506-046 (S) Syntax error.
Yes, that's because of a
On Wed, Jan 20, 1999, [EMAIL PROTECTED] wrote:
Full_Name:
Version: 2.1.7-1.3.4
OS: AIX 4.2 / apache 1.3.4
Submission from: felix.adpcl.com (194.98.137.100)
Error when compiling ca-fix.c
example:
make certificate TYPE=test
+ finding random files on your platform
+ building ca-fix
Ralf S. Engelschall wrote:
It's fine, I tracked things down. The wrong key file had been copied
over to the production server, so it didn't match the crt. Thanks for
the advice in any case!
Oh, that's good news ;-)
Then it was just some sort of a configuration error...
Yes --
Full_Name: Andrew J Cosgriff
Version: 2.1.7
OS: Digital Unix 4.0D
Submission from: proxy.monash.edu.au (130.194.11.7)
Upgrading from apache 1.2.6+ben'ssl to 1.3.4 + mod_ssl 2.1.7
has caused me a fair bit of grief - everything seems fine
(i'd done the upgrade on Solaris boxes with no problems)
On Tue, Jan 19, 1999, Shane Wegner wrote:
I have setup mod_ssl with Apache 1.3.4 on my web server according to the
instructions in the INSTALL file. I used a self-signed key with "make
certificate TYPE=custom" and it worked in lynx without a problem. Tests
in s_client showed a 1024 bit
On Wed, Jan 20, 1999, [EMAIL PROTECTED] wrote:
[...]
Upgrading from apache 1.2.6+ben'ssl to 1.3.4 + mod_ssl 2.1.7
has caused me a fair bit of grief - everything seems fine
(i'd done the upgrade on Solaris boxes with no problems)
but as soon as i try and connect to the https port through my
Hi,
I have setup mod_ssl with Apache 1.3.4 on my web server according to the
instructions in the INSTALL file. I used a self-signed key with "make
certificate TYPE=custom" and it worked in lynx without a problem. Tests
in s_client showed a 1024 bit key. I then fired up the win95 machine and
On Tue, Jan 19, 1999, James H.G. Redekop wrote:
[...]
Usually it doesn't matter where it was generated, because the format
and encoding is standardized. What you should do is to run the
commands
$ ssleay x509 -noout -text -in server.crt
$ ssleay rsa -noout -text -in
On Tue, Jan 19, 1999, James H.G. Redekop wrote:
[...]
Usually it doesn't matter where it was generated, because the format
and encoding is standardized. What you should do is to run the
commands
$ ssleay x509 -noout -text -in server.crt
$ ssleay rsa -noout -text -in
11 matches
Mail list logo