----- Original Message ----- > On Sun May 05 23:40:18 2013, [email protected] wrote: > > Hi, > > > > found in the current git version. > > > > RFC 6347, Sect. 4.2.2 says: > > The first message each side transmits in each handshake always has > > message_seq = 0. Whenever each new message is generated, the > > message_seq value is incremented by one. Note that in the case of a > > rehandshake, this implies that the HelloRequest will have message_seq > > = 0 and the ServerHello will have message_seq = 1 > > > > When a OpenSSL DTLS server requests a rehandshake, it correctly sends a > > HelloRequest with message_seq = 0, the next ServerHello should have > > message_seq = 1, but OpenSSL sends it with message_seq = 0. This clearly > > violates the RFC. > > > > Do you get that with the 1.0.2 branch too? > > Note that the master branch has been extensively revised and there may be the > odd bug lurking in there.
Just build and tested it. Yes, the problem is in the 1.0.2 branch too. BTW: I tried with gnutls and they send the ServerHello that follows the HelloRequest with message_seq = 1. Andreas > > Steve. > -- > Dr Stephen N. Henson. OpenSSL project core developer. > Commercial tech support now available see: http://www.openssl.org > > -- -- Dipl. Inform. Andreas Schultz -------------------------------------------------------------- ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [email protected] Automated List Manager [email protected]
