Bug#426013: exim4-daemon-heavy Base64 decoding error

[Andreas Metzler]

On 2007-05-25 Mark Adams <mark at campbell-lange.net> wrote:
> On Fri, May 25, 2007 at 07:32:14PM +0200, Andreas Metzler wrote:
>> On 2007-05-25 Mark Adams <mark at campbell-lange.net> wrote:
...]
>>> Currently trying to setup SMTPS with a comodo ssl certificate. This is
>>> an RSA cert encoded as Base64. The following error is received;

>>> 2007-05-13 22:02:17 TLS error on connection from myhost.net [217.147.xx.xx]
>>>     (cert/key set up: cert=/etc/exim4/certificates/newserver_co_uk.crt
>>>      key=/etc/exim4/certificates/newserver_co_uk.pem) : Base64 decoding error.
>> [...]

>> Is the key in PEM format?

>> If it is in PKCS#8 format (Notable by "-----BEGIN ENCRYPTED
>> PRIVATE KEY-----" instead of "BEGIN RSA PRIVATE KEY") converting
>> with openssl pkcs8 might help.


> Yes the key does begin with "BEGIN RSA PRIVATE KEY"

> I had noted the post regarding PKCS8, this sounds very much like the
> same issue except my key does appear to be RSA. Is there anyway that I
> can confirm this?

If "openssl pkcs8  <  exim.key" works then the key is in PKCS8, otherwise
it is not and "openssl rsa  <  exim.key" should work.

Does 
openssl s_server -debug -key exim.key -cert exim.crt
work?
And how about
gnutls-serv --debug 5 --x509keyfile exim.key --x509certfile exim.crt
cu andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'