[openssl-dev] Running against BoringSSL's SSL test suite
kotamarthyd at gmail.com
Thu Mar 10 06:30:23 UTC 2016
And also Openssl fails with Resume-Client-NoResume cases. Do you have
any report on which test cases do fail and reasons for the failure?
RT tickets 4387 through 4395 were the failures I've triaged. I'm sure
there's more things in there to look through.
I don't believe Resume-Client-NoResume fails for me. Perhaps something was
fixed between master and 1.1.0-pre2.
Openssl doesn't gives any error. For Resume-Client-NoResume-SSL3-TLS11 test
case, we expect the new session's handshake to be done with TLS11. But with
Openssl handshake is done using SSL3. As in ssl3_clear, we set back
s->version to s->method->version.
On Wed, Mar 9, 2016 at 10:38 PM, David Benjamin <davidben at google.com> wrote:
> On Wed, Mar 9, 2016 at 5:07 AM Kanaka Kotamarthy <kotamarthyd at gmail.com>
>> I am even testing OpenSSL with BoringSSL's test cases using
>> Openssl-1.1.0-pre2. Trying to find out reasons of OpenSSL's failures
>> for particular cases.
>> DTLS 1.0 session resumption has some thing wrong. If s_server started
>> with -dtls and s_client -dtls1 -reconnect , session resumption is not
>> being done. The reason for this may be, version negotiation for DTLS
>> is done after loading previous session and check for s->version and
>> s->session->version fails in tls_process_client_hello.
> See RT #4392.
>> And also Openssl fails with Resume-Client-NoResume cases. Do you have
>> any report on which test cases do fail and reasons for the failure?
> RT tickets 4387 through 4395 were the failures I've triaged. I'm sure
> there's more things in there to look through.
> I don't believe Resume-Client-NoResume fails for me. Perhaps something was
> fixed between master and 1.1.0-pre2.
>> Thank you
>> On Tue, Mar 8, 2016 at 3:19 AM, David Benjamin <davidben at google.com>
>> > Hi folks,
>> > So, we've by now built up a decent-sized SSL test suite in BoringSSL. I
>> > bored and ran it against OpenSSL master. It revealed a number of bugs.
>> > is https://github.com/openssl/openssl/pull/603. I'll be filing tickets
>> > shortly for the remaining ones I've triaged, but I thought I'd send this
>> > separately rather than duplicate it everywhere.
>> > Emilia also suggested there may be room to collaborate on testing. If
>> > nothing else, just borrowing ideas or porting tests to/from your
>> > setup. (Like, say, the ones that caught the bugs I'll be reporting. :-)
>> > So, here's an introduction on how it all works:
>> > To run the tests on OpenSSL, clone BoringSSL:
>> > https://boringssl.googlesource.com/boringssl/
>> > Then patch in this change. (Click the "Download" in the upper-right for
>> > options.)
>> > https://boringssl-review.googlesource.com/#/c/7332/
>> > Then follow the instructions in the commit message.
>> > The tests themselves and the runner logic live in
>> > They work by running an unmodified TLS stack in a shim binary against a
>> > of Go's. We patch our copy with options for weird behavior to test
>> > Go and shim communicate entirely with sockets and (tons of) command-line
>> > flags, though it is slightly overfit to BoringSSL's behavior and checks
>> > error strings a lot. The shim also has options like -async mode which
>> we use
>> > on a subset of tests to stress state machine resumption. (This has
>> saved me
>> > from state machine bugs so many times.)
>> > I hope this is useful! Bugs and patches will follow this mail, as I
>> > them up.
>> > David
>> > --
>> > openssl-dev mailing list
>> > To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
>> openssl-dev mailing list
>> To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
> openssl-dev mailing list
> To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the openssl-dev