I'm also speaking out of turn, but having both ends trying to be both server and client *on the same connection* just does not make sense, TLS or DTLS.
Sent from my BlackBerry 10 smartphone on the Verizon Wireless 4G LTE network. Original Message From: Jeffrey Walton Sent: Sunday, June 19, 2016 09:59 To: OpenSSL Users Reply To: noloa...@gmail.com Subject: Re: [openssl-users] Fwd: issue with dtls failure during openssl upgrade from 1.0.1m to q On Sun, Jun 19, 2016 at 9:47 AM, Test ssl <testossl2...@gmail.com> wrote: > Hi Matt, > > This is a DTLSv1.0 connection, so the hosts on both sides will connect to > each other acting as both TLS client and TLS server. > > We think the dtls failure is due to cipher suites. But we are not able to > understand why it works for 1.0.1m with same certificate. > > Please help us. I don't mean to speak out of turn, but you are not giving Matt too much to work with. Perhaps you could put together a minimum sample program which demonstrates the problem? Or maybe give him s_server and s_client commands to duplicate it? Jeff -- openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
smime.p7s
Description: S/MIME cryptographic signature
-- openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
