<div dir="ltr"><br><div class="gmail_extra">Hello!</div><div class="gmail_extra"><br></div><div class="gmail_extra"><div class="gmail_quote">2018-01-01 1:23 GMT+01:00 asdf asdf <span dir="ltr"><<a href="mailto:codewiget95@gmail.com" target="_blank">codewiget95@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<div name="messageBodySection" style="font-size:14px;font-family:-apple-system,BlinkMacSystemFont,sans-serif">Hello,
<div><br></div>
<div>I saw a post from a few months ago here: <a href="http://erlang.org/pipermail/erlang-questions/2017-August/093136.html" target="_blank">http://erlang.org/<wbr>pipermail/erlang-questions/<wbr>2017-August/093136.html</a> about adding support for TLS 1.3 to the new OTP, and I am curious about the status of this and how I could get involved. I have made a deal of modifications to the underlying OTP ssl module to suit my businesses needs, and I believe I could help in the development. <br></div></div></div></blockquote><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div name="messageBodySection" style="font-size:14px;font-family:-apple-system,BlinkMacSystemFont,sans-serif">
<div><br></div>
<div>In the post I linked, the responder mentioned that there are many unknowns with the new TLS implementation, which is definitely true, but there are those who have implemented it successfully - both WolfSSL and OpenSSL support this (C implementation).</div>
<div><br></div>
<div>TLS 1.3 has huge advantages for embedded/iot devices - it reduces the number of RTTs which is huge for customers with data and processing constraints. For companies managing millions of devices, this would add huge cost savings, not to mention the increased levels of security. This will be a great advantage for Erlang to have.</div>
<div><br></div>
<div>Is there any work being done currently on development, and is it possible for a Non-Erricson employee to contribute?</div>
<div><br></div>
<div>Thanks for your help</div>
<div><br></div>
</div>
</div>
</blockquote></div></div><div class="gmail_extra"><br></div><div class="gmail_extra">The way you may contribute is to make PR (pull requests). My team is responsible for TLS development and we have done some preparations for TLS-1.3 but we have not added any TLS-1.3 specific code yet. <br></div><div class="gmail_extra">The latest changes was to handle cipher suites as maps instead of tuples internally.We are thinking of moving the API that way too. To make contributing easier for us both if would be helpful if you can make small logical steps</div><div class="gmail_extra">implementing some part of the code needed for TLS-1.3 support. If you need/want to make changes the does not follow the current design send me a mail at <a href="mailto:ingela@erlang.org">ingela@erlang.org</a> so we can consider what will be best and also fit our plans.</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></div><div class="gmail_extra"><br></div><div class="gmail_extra"><br></div><div class="gmail_extra"><br></div></div>