Re: sslio error description incomplete/wrong

On Wed, 5 Jan 2005, Gerrit Pape wrote:

> > I'm thinking that sslio shouldn't have reported this as "no error". I 
> > guess this is a martixSsl library problem, but I thought i should report 
> > anywhere.
> 
> Yes, makes no sense to report through errno here, I'll take a look at
> it.  The code also can be optimized, no need to try to send a closure
> alert in this case.  Thanks for the notice.

My pleasure. Thanks for the code!

> >    TLS 1.0 clients that support SSL Version 2.0 servers must send SSL
> >    Version 2.0 client hello messages [SSL2]. TLS servers should accept
> >    either client hello format if they wish to support SSL 2.0 clients on
> >    the same connection port. The only deviations from the Version 2.0
> >    specification are the ability to specify a version with a value of
> >    three and the support for more ciphering types in the CipherSpec.
> > 
> > Evolution was the worst. It sent an SSLv2 client hello (seemingly implying 
> > that it would talk to SSLv2 servers, then dropped the connection when the 
> > server replied with an SSLv3.0 server hello. No useful diagnostics 
> > available at either end.
> 
> Hmm, what's the reason you need tls, and don't run a separate service on
> the imap/ssl or smtp/ssl port?

For completeness. And the challenge. 

---
Charlie