Github pull 570 which was associated with this ticket has been closed, so
closing this too.
Matt
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4201
Please log in as guest with password guest if prompted
--
openssl-dev mailing list
To unsubscribe:
I have updated Judson's patch to match with master branch. See GitHub PR
https://github.com/openssl/openssl/pull/570
Jan
On Mon, Jan 11, 2016 at 12:34 PM, Judson Wilson via RT
wrote:
> Here is an OpenSSL port of a patch in BoringSSL. It requires a call from
> the application
It automatically opens a BIO for the keylogfile. Also if this patch is
merged, RT 3352 can be reverted because it covers only a special case in
the s_client app.
On Tue, Jan 19, 2016 at 8:33 PM, Jan Žák wrote:
> I have updated Judson's patch to match with master branch. See
On Mon Dec 28 23:53:02 2015, matt wrote:
> On Mon Dec 28 22:01:04 2015, rs...@akamai.com wrote:
> > Yes we would be interested in this but someone would almost
> > definitely
> > have to be provided as a complete patch because it seems unlikely
> > anyone on the team will get around to doing it by
Here is an OpenSSL port of a patch in BoringSSL. It requires a call from
the application to set a file BIO. You could probably do this from within
SSL_CTX_new or something like that if you want a solution that doesn't
change the application.
Here is an OpenSSL port of a patch in BoringSSL. It requires a call from
the application to set a file BIO. You could probably do this from within
SSL_CTX_new or something like that if you want a solution that doesn't
change the application.
This implementation is not enough, beacuse it works only for openssl
s_client app. However it should work for all apps using openssl as a
library (eg. curl, nginx).
SSLKEYLOGFILE env var is a good current standard, so I think openssl should
use it as well.
Regards,
Jan Zak
On Tue, Dec 29, 2015
> SSLKEYLOGFILE env var is a good current standard, so I think openssl should
> use it as well.
Patches to implement all of this would be helpful, otherwise it will probably
not make it into the next relese.
___
openssl-dev mailing list
To
Yes we would be interested in this but someone would almost definitely have to
be provided as a complete patch because it seems unlikely anyone on the team
will get around to doing it by 1.1 release.
___
openssl-dev mailing list
To unsubscribe:
Yes we would be interested in this but someone would almost definitely have to
be provided as a complete patch because it seems unlikely anyone on the team
will get around to doing it by 1.1 release.
___
openssl-dev mailing list
To unsubscribe:
On Mon Dec 28 22:01:04 2015, rs...@akamai.com wrote:
> Yes we would be interested in this but someone would almost definitely
> have to be provided as a complete patch because it seems unlikely
> anyone on the team will get around to doing it by 1.1 release.
>
Actually I think this capability is
Many HTTPS browsers support dumping keys for TLS sessions to a text file to
allow analysis tools to decrypt captured TLS sessions. This is an extremely
useful debugging tool for working with services that only expose encrypted
interfaces. This support exists in Firefox and Chrome: in Firefox’s
12 matches
Mail list logo