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
QTEVMBMGA1UECBMMV2VzdGVybiBDYXBlMRIwEAYDVQQHEwlDYXBlIFRvd24xHTAb
BgNVBAoTFFRoYXd0ZSBDb25zdWx0aW5nIGNjMSgwJgYDVQQLEx9DZXJ0aWZpY2F0
aW9uIFNlcnZpY2VzIERpdmlzaW9uMRkwFwYDVQQDExBUaGF3dGUgU2VydmVyIENB
MSYwJAYJKoZIhvcNAQkBFhdzZXJ2ZXItY2VydHNAdGhhd3RlLmNvbTAeFw05OTA5
MTMxMzM0NDVaFw0wMDA5MjYxMzM0NDVaMIGRMQswCQYDVQQGEwJVUzEQMA4GA1UE
CBMHRmxvcmlkYTEOMAwGA1UEBxMFTWlhbWkxGjAYBgNVBAoTEUZyZWVsYW5jZSBT
dWNjZXNzMSEwHwYDVQQLExhTZWN1cmUgU2VydmljZXMgRGl2aXNpb24xITAfBgNV
BAMTGHd3dy5mcmVlbGFuY2VzdWNjZXNzLmNvbTBcMA0GCSqGSIb3DQEBAQUAA0sA
MEgCQQC8bvTfSBgoKNaqMlXUv7Fr4GVNWY/6CuriCtggMeC0BqSKq021bhwfo3DL
oav8rGbLJBvbbSwa89P0FUvf0pj5AgMBAAGjJTAjMBMGA1UdJQQMMAoGCCsGAQUF
BwMBMAwGA1UdEwEB/wQCMAAwDQYJKoZIhvcNAQEEBQADgYEALt7627Hs+30X4Kc9
k1OyppVfE3i2JcgzpF5ZVF1pd1JCkAiSlKh94EnmIWbgZpImvZSeZgixYhT6bMXS
7N53vuMpWKdlMhdXb1aWX2y157aeAlVvGv3jFePejaNzw7SUDdsuplabE8r11n4l
UMtE1UKmRQBKQua/WLReskiWrVM=
-----END CERTIFICATE-----
I really appreciate the help...
My original posting contains the errors I receive from the Makefile
in 'ssl.crt'.
http://www.progressive-comp.com/Lists/?l=apache-modssl&m=93808996711717&w=2
Thanks again,
Chris
At 10:00 AM 9/28/1999 +0200, you wrote:
>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 said to remove the X590, but it isn't there. The new cert from
> > Thawte doesn't have this in the header and it still won't work.
> > Please again see my original message.
> >
> > http://www.progressive-comp.com/Lists/?l=apache-modssl&m=93808996711717&w=2
> >
> > The main problem is that the 'Makefile' in 'ssl.crt' doesn't
> > recognize the new style v3 cert from Thawte and thus will not
> > create a "hash link" for it.
>
>Errr.. the Makefile uses "openssl x509" command and this one _DOES_ understand
>x509v3 certs, of course. Hmmm... can you post your certificate (not the key,
>only the cert, of course) so we can have a more closer look at this particular
>cert and to find out why the hash isn't created?
>
> Ralf S. Engelschall
> [EMAIL PROTECTED]
> www.engelschall.com
>______________________________________________________________________
>Apache Interface to OpenSSL (mod_ssl) www.modssl.org
>User Support Mailing List [EMAIL PROTECTED]
>Automated List Manager [EMAIL PROTECTED]
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
