[PATCH] OpenSSL: BoringSSL has SSL_get_client_random, etc.

David Benjamin davidben at google.com
Thu May 5 10:43:42 PDT 2016

Attached since I trust my mail client to completely destroy the whitespace.

Apologies for making your #ifdef soup even messier. The motivation
here is we'd like to opaquify the SSL structs in BoringSSL (which
should, in the long run, make wpa_supplicant less sensitive to changes
on our end). To keep things simple, I'm mirroring OpenSSL 1.1.0's
APIs. But, for the moment, BoringSSL's OPENSSL_VERSION_NUMBER still
claims to be 1.0.2, so this will need some more conditionals.

I'm optimistic that someday we'll mimic enough of 1.1.0 that bumping
OPENSSL_VERSION_NUMBER might make sense and then we won't need this
special-case. For now, it and the ecosystem are enough of a moving
target that I don't think it's feasible just yet.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-OpenSSL-BoringSSL-has-SSL_get_client_random-etc.patch
Type: text/x-patch
Size: 1941 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/hostap/attachments/20160505/7876e2d4/attachment.bin>

More information about the Hostap mailing list