<div dir="ltr"><div class="gmail_extra">Hi!<br><br><div class="gmail_quote">2017-01-13 11:43 GMT+01:00 Roger Lipscombe <span dir="ltr"><<a href="mailto:roger@differentpla.net" target="_blank">roger@differentpla.net</a>></span>:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="gmail-">On 13 January 2017 at 09:39, Ingela Andin <<a href="mailto:ingela.andin@gmail.com">ingela.andin@gmail.com</a>> wrote:<br>
> Well our reasoning at the moment is that we could add a debug possibility,<br>
> that would let connection_information<br>
</span><span class="gmail-">> return client/server/master_secret values for connections started in debug<br>
> mode. Just like you can configure a connection to run anonymous ciphers<br>
> suites for test and debugging purposes. However we would<br>
> not want connection_information to return these values by default. Even if<br>
> you conceptually can get at the information by hacking we do not want to<br>
> make it easy to do bad things to security by "accident" or<br>
> otherwise.<br>
<br>
</span>Sure. There's precedent for that: process_info/1 doesn't return<br>
everything that you can ask for in process_info/2, no?<br>
<br>
I'm not sure how this would do bad things to security. The server's<br>
already seeing the plaintext, otherwise it couldn't do its job. Could<br>
you explain your concerns further?<br></blockquote><div><br><br></div><div>As long as it stays on the server.... TLS is suppose to provide peer to peer security<br></div><div>and you are not suppose to be able to read TLS data in traffic sniffing logs. <br></div><div>What if someone decides to transfer the logs in an insecure way from the server!<br><br></div><div>What if someone thinks its a good idea to decrypt the data outside the TLS connection in the server<br></div><div>and send it to an external logging server in the clear!<br></div><div><br></div><div>Openssl also warns for missuse:<br><a href="https://www.openssl.org/docs/man1.1.0/ssl/SSL_SESSION_get_master_key.html">https://www.openssl.org/docs/man1.1.0/ssl/SSL_SESSION_get_master_key.html</a><br></div><div> </div></div>When it comes to security you should be very careful is all I am saying, and providing a way for others<br></div><div class="gmail_extra">to use secret information in a not intended way is potentially dangerous. <br></div><div class="gmail_extra"><br></div><div class="gmail_extra">Regards Ingela Erlang/OTP Team - Ericsson AB<br></div><div class="gmail_extra"><br><br></div><div class="gmail_extra"><br><br><br><br><br></div></div>