On Thu, Sep 30, 1999, WSO Support wrote:
The problem was that at the top of the Makefile script
in 'ssl.crt' the variable SSL_PROGRAM was undefined. I'm
not sure why?
I replaced it with:
SSL_PROGRAM=/usr/local/bin/openssl
And everything works great!
Thanks for your
The problem was that at the top of the Makefile script
in 'ssl.crt' the variable SSL_PROGRAM was undefined. I'm
not sure why?
I replaced it with:
SSL_PROGRAM=/usr/local/bin/openssl
And everything works great!
Thanks for your help and patience!
-Chris
At 09:42 PM 9/28/1999 +0200, you wrote:
On Wed, Sep 29, 1999, WSO Support wrote:
The problem was that at the top of the Makefile script
in 'ssl.crt' the variable SSL_PROGRAM was undefined. I'm
not sure why?
I replaced it with:
SSL_PROGRAM=/usr/local/bin/openssl
And everything works great!
Thanks for your help and patience!
Confusing. The variable is intentionally undefined there. Because if called
from the top-level the top-level provides this variable (by overiding it on
the "make" command line). And even if you run the "make" locally the embedded
shell script finds a reasonable "openssl" or "ssleay" program in
On Wed, Sep 29, 1999, Jon Earle wrote:
Sorry, I've cut pasted it into a `x.crt' file in a ssl.crt/ directory, ran
`make' there and got no error. Instead I got a correct hash symlink
Maybe a stupid question, but why is this symlink of importance? I've got 2
certs and keys working fine
Thanks for the response, but it seems you've misunderstood me.
Now, I took a look at the certs, I noticed that all of them
start with "-BEGIN X509 CERTIFICATE-". When I originally
got these from Thawte, the header was "-BEGIN CERTIFICATE-".
Yes, OpenSSL looks for "BEGIN
On Mon, Sep 27, 1999, WSO Support wrote:
[...]
The *new* cert I have from Thawte starts with just
"-BEGIN CERTIFICATE-", as all of the others I have ever
gotten in the past from Thawte. The only difference now is that
this is a v3 cert, not v1, as all these others were.
You
Yes, here is the cert I'm having the problem with. I've had
Thawte triple check it, and they have found no problems. This
is a cert for a client of mine, of course.
-BEGIN CERTIFICATE-
MIICsDCCAhmgAwIBAgIDAIPNMA0GCSqGSIb3DQEBBAUAMIHEMQswCQYDVQQGEwJa
On Tue, Sep 28, 1999, WSO Support wrote:
Yes, here is the cert I'm having the problem with. I've had
Thawte triple check it, and they have found no problems. This
is a cert for a client of mine, of course.
-BEGIN CERTIFICATE-
On Wed, Sep 22, 1999, WSO Support wrote:
[...]
I get the following error:
unable to load certificate
error:0906906C:PEM routines:PEM_read:no start line
Now, I took a look at the certs, I noticed that all of them
start with "-BEGIN X509 CERTIFICATE-". When I originally
got these
I've just installed Apache 1.3.9+OpenSSL_0.9.4+mod_ssl_2.4.2
I moved my existing certs (issued by VeriSign Thawte) into
the /usr/local/apache/conf/ssl.crt directory. I moved my
existing .key files into 'ssl.key'.
I then ran 'make' from inside the 'ssl.crt' directory to create
the hash symlink
11 matches
Mail list logo