Tom Biggs wrote:
=================================================================
>I'm not an expert on this, but the first thing I'd try, if I got
>a "bad end line" error message, would be to check the
>file and see what the line terminators were.  It sounds
>like it either is expecting a newline char at the end of
>some line, or, it's choking on an unexpected newline char.
>
>Or maybe the file is truncated, or maybe it just wants
>one more newline at the end...
=================================================================

Seems like the appropriate line ending is there:
-----END CERTIFICATE-----  (with a newline at the end of this line)

Also extra new lines don't seem to affect the outcome.

Jeff Cornett wrote:
=================================================================
>It is possible that a Verisign certificate is not compatible with OpenSSL.
>Perhaps someone else can confirm or deny this.
>
>I have been experimenting with OpenSSL and a product from Rick Kaseguma
>called SSLWrap.  In Rick's documentation
>(http://www.rickk.com/sslwrap/index205.htm) he says: "Verisign previously
>would not issue a certificate for a server using ssleay; though this may
>have changed."
=================================================================

Verisign now includes instructions for Apache/ssleay (by which I think it
means the mod_ssl/OpenSSL combination).

Any other ideas?  Does Ulf Moeller, Richard Levitte, Bodo Moeller or
Dr Stephen N Henson have any idea what the error message means?  I see their
names appearing often on this list.

Paul E Wilt 
Principal Software Engineer
____________________________________________________
XanEdu, Inc. ( a division of Bell+Howell Information&Learning)
http://www.XanEdu.com
mailto:[EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
300 North Zeeb Rd                       Phone: (734) 975-6021  (800)
521-0600 x6021
Ann Arbor, MI 48106             Fax:    (734) 973-0737
____________________________________________________



-----Original Message-----
From: Tom Biggs [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, December 06,2000 11:50 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: Experiencing error when installing a Verisign certificate!


At 11:35 AM 12/6/00 -0500, Wilt, Paul wrote:
>We recently needed to update our Verisign certificate for our secure site.
>We are switching from Netscape to Apache mod_ssl/OpenSSL.
>We are attempting to install the Verisign certificate that we received
>...
>[04/Dec/2000 12:09:24 5523600] [error] OpenSSL: error:0906D066:PEM
>routines:PEM_read_bio:bad end line
>[04/Dec/2000 12:09:24 5523600] [error] OpenSSL: error:0B084009:x509
>certificate routines:X509_load_cert_crl_file:missing asn1 eos
>
>
>Does anyone know what the error message means?

I'm not an expert on this, but the first thing I'd try, if I got
a "bad end line" error message, would be to check the
file and see what the line terminators were.  It sounds
like it either is expecting a newline char at the end of
some line, or, it's choking on an unexpected newline char.

Or maybe the file is truncated, or maybe it just wants
one more newline at the end...


((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((
Tom Biggs
'89 FJ1200     DoD #1146

"The whole aim of practical politics is to keep the populace alarmed -
and hence clamorous to be led to safety - by menacing it with an endless
series of hobgoblins, all of them imaginary."  -- H.L. Mencken
))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))

______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
User Support Mailing List                    [EMAIL PROTECTED]
Automated List Manager                           [EMAIL PROTECTED]
______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
User Support Mailing List                    [EMAIL PROTECTED]
Automated List Manager                           [EMAIL PROTECTED]

Reply via email to