[Serdev] Using TLS with Windows Messenger..

[Cesc]

Yes ... SER proxy and your Windows messenger UA do not share any cipher, so 
they cannot communicate, thus the SSL connection is tore down. 
 In the config file you can specify which ciphers SER will use, but i would 
say that the default ones are pretty much the ones everybody uses, thus i 
don't know why it causes this error. 
 You could try to to use ssldump to get a list of the ciphers being 
negotiated ... or you can use ethereal, capture the traffic and i will try 
to figure out ... 
 Regards,
 Cesc

 On 9/20/05, Alejandro Falcón <alejandrocfg at gmail.com> wrote: 
> 
> Im testing SER with TLS with Windows Messenger but a get this error in SER 
> en the UA try to connect: 
> 
> 19(30955) tls_accept: Error in SSL:
> 19(30955) tls_error: error:1408A0C1:SSL routines:SSL3_GET_CLIENT_HELLO:no 
> shared cipher
>  Anybody knows what happpen here??
>   THANKs
> -- 
> ALE. 
> 
> _______________________________________________
> Serdev mailing list
> Serdev at iptel.org
> http://mail.iptel.org/mailman/listinfo/serdev
> 
> 
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.iptel.org/pipermail/serdev/attachments/20050920/c4038a17/attachment.htm