Mark Adams <[EMAIL PROTECTED]> writes: > Hi Simon, Thanks for the reply. > > Apologies for the confusion, I renamed .pem to .key in the middle of the > process for my own clarification. the Certificate file does look like > that, except it is much longer, atleast twice as long. it starts with > the BEGIN line and ends with the END line.
Yeah, the size for a real certificate will likely be much larger. That was a short test certificate. > The .key file also begins with the BEGIN RSA PRIVATE KEY and ends with > the right line. > > when I run certtool -k < newserver_co_uk.key the beginning starts with > > Public Key Info: > Public Key Algorithm: RSA > > when I run certool -i < newerver_co_uk.crt It begins with the following > output > > X.509 Certificate Information: > Version: 3 > Serial Number (hex): 78712b9b85f057731ea88fb1b9527153 > Issuer: C=US,ST=UT,L=Salt Lake City,O=The USERTRUST > Network,OU=http://www.usertrust.com,CN=UTN-USERFirst-Hardware > Validity: > Not Before: Thu May 10 00:00:00 UTC 2007 > Not After: Sat May 9 23:59:59 UTC 2009 > Subject Public Key Algorithm: RSA Excellent, thank you. Could you also cut'n'paste your current exim (MAIN_TLS_*) configuration? Which exim version are you using? Still 4.63-17? It would help if you could post a short snippet of an updated error message, with the new filenames and so on. When do the problem actually happen? Does it happen on all TLS sessions, or just some? /Simon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
