Ok, I’ve proposed an initial patch at
https://github.com/openssl/openssl/pull/1646
I’d like some feedback about how best to test this functionality, but initially
this does appear to work.
Cory
> On 28 Sep 2016, at 13:30, Salz, Rich wrote:
>
>> [0]:
>> https://commondatastorage.googleapis.c
> [0]:
> https://commondatastorage.googleapis.com/chromium-boringssl-docs/ssl.h.html#SSL_CTX_set_keylog_callback
That seems like a reasonable thing to put into the next release.
--
Senior Architect, Akamai Technologies
Member, OpenSSL Dev Team
IM: richs...@jabber.at Twitter: RichSalz
--
op
> On 28 Sep 2016, at 11:11, Cory Benfield wrote:
>
> So what do the OpenSSL developers think? Do we need the compile flag, or is
> some lower bar sufficient?
It was brought to my attention that BoringSSL takes an alternative approach to
this problem: they allow users to register a callback fo
All,
Some time ago I posted noting that it would be useful to have the SSLKEYLOGFILE
environment variable supported by OpenSSL. I lost track of that request, and
have since noticed that a patch that would have added support for that
environment variable[0] was closed, with Rich asking for an al
