Re: ssl certificate failure
John H Meyers
> When I try to send mail in Eudora I get:
> the server's SSL Certificate was rejected...
> I am using charter.net as my email
> What does all this mean?
The obviously bogus certificate seems to indicate
that someone at Charter.net is experimenting with their server(s).
Did Charter.net ever tell you that they support SSL,
or instruct you to tell your email client to use SSL?
You didn't say whether this involved sending or receiving,
but whichever it is, if your current "Secure Sockets while
Sending (or Receiving)" setting is "If Available, STARTTLS,"
just change it to "Never."
The "if available" setting in Eudora will suddenly switch
from never using SSL to always trying to use SSL
if the server suddenly starts advertising that it supports SSL,
even if the ISP is simply experimenting,
and isn't really ready to offer any such service.
--
John H Meyers
since the original post is not going to be archived:
> Data:
> Version: 3 (0x2)
> Serial Number: 0 (0x0) <===
> Signature Algorithm: md5WithRSAEncryption
> Issuer: C=US, O=RTFM, Inc., OU=Widgets Division, CN=Test <===
> CA20010517
> Validity
> Not Before: May 17 16:01:14 2001 GMT
> Not After : Dec 25 16:01:14 2006 GMT <===
> Subject: C=US, O=RTFM, Inc., OU=Widgets Division, CN=Test <===
> CA20010517
[remainder is irrelevant]
> Subject Public Key Info:
> Public Key Algorithm: rsaEncryption
> RSA Public Key: (1024 bit)
> Modulus (1024 bit):
> 00:9a:45:f8:d3:06:ab:98:7d:3e:96:7c:03:f5:88:
> ec:26:14:73:65:7e:aa:5d:a7:45:af:2d:32:da:da:
> d9:ea:03:2c:f0:cb:f7:dc:82:8f:c0:eb:bc:4c:4e:
> d5:fb:73:c4:48:4b:63:23:6c:2b:f2:3b:95:f4:e9:
> 1b:20:f3:a6:fa:d7:79:33:cf:ba:bd:7c:88:5b:e2:
> 41:a3:77:21:f7:d8:b4:40:c4:df:e7:f8:d3:82:c5:
> be:dc:88:d5:f3:21:1d:88:67:19:16:9d:8d:58:a2:
> d1:bd:93:ea:d9:54:5b:b8:5e:d1:d6:9b:e0:71:a4:
> 6e:04:9d:30:18:ea:21:c2:7b
> Exponent: 65537 (0x10001)
> Signature Algorithm: md5WithRSAEncryption
> 94:07:cc:cc:28:89:57:e6:2a:3c:4d:a9:5b:cc:7f:50:91:ee:
> c1:72:f1:40:2f:ec:29:ff:9c:35:4e:85:6c:5a:43:6b:20:d4:
> 96:2a:fe:9b:97:f8:dc:a8:e0:f7:68:f8:4a:ee:a8:5a:78:e5:
> 3c:65:62:8b:3e:83:cf:0a:74:65:f5:6a:3e:d4:9b:6c:38:ed:
> ea:22:02:4f:ef:d0:65:f6:8a:0b:19:a8:62:c4:5d:af:fe:07:
> 9a:e6:a3:48:4a:34:2f:c1:89:65:2d:26:bf:fc:03:cf:ea:45:
> c7:9e:03:b4:44:84:5b:89:30:58:1d:29:00:ce:6e:a1:0d:db:
> 2f:54
>
> I am using charter.net as my email
> What does all this mean?
It appears as if Charter.net is experimenting,
and isn't really ready to provide SSL,
or that they accidentally restored their server back a few years :)
Again, adjust "Secure Sockets when Sending" (or Receiving),
changing "If Available, STARTTLS" to "Never"
--