<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><span class="senderContainer" style="margin: 0px; padding: 0px; word-wrap: break-word; font-family: LucidaGrande; text-indent: -66.92578125px;"> </span><span style="font-family: LucidaGrande; text-indent: -66.92578125px; background-color: rgb(255, 255, 255);" class=""></span><span class="innerMessage" style="margin: 0px; padding: 0px; word-wrap: break-word; font-family: LucidaGrande; text-indent: -66.92578125px;">Hey All,</span><div class=""><span class="innerMessage" style="margin: 0px; padding: 0px; word-wrap: break-word; font-family: LucidaGrande; text-indent: -66.92578125px;"><br class=""></span></div><div class=""><span class="innerMessage" style="margin: 0px; padding: 0px; word-wrap: break-word; font-family: LucidaGrande; text-indent: -66.92578125px;">I'm a collaborator on the Node.js project. Another collaborator sent a fix that has landed upstream to allow different protocol versions when reusing sessions. </span></div><div class=""><span class="innerMessage" style="margin: 0px; padding: 0px; word-wrap: break-word; font-family: LucidaGrande; text-indent: -66.92578125px;"><br class=""></span></div><div class=""><span class="innerMessage" style="margin: 0px; padding: 0px; word-wrap: break-word; text-indent: -66.92578125px;"><font face="LucidaGrande" class=""><a href="https://github.com/openssl/openssl/pull/852" class="">https://github.com/openssl/openssl/pull/852</a></font></span></div><div class=""><span class="innerMessage" style="margin: 0px; padding: 0px; word-wrap: break-word; text-indent: -66.92578125px;"><font face="LucidaGrande" class=""><br class=""></font></span></div><div class=""><span class="innerMessage" style="margin: 0px; padding: 0px; word-wrap: break-word; text-indent: -66.92578125px;"><font face="LucidaGrande" class="">We are currently experiencing problems with Node.js interacting with dynamoDB </font></span><span style="text-indent: -66.92578125px; font-family: LucidaGrande;" class="">for people trying to use Lamda on AWS. Lamda is running on node v4, which is using openssl 1.0.2.</span></div><div class=""><span style="text-indent: -66.92578125px; font-family: LucidaGrande;" class=""><br class=""></span></div><div class=""><span style="text-indent: -66.92578125px;" class=""><font face="LucidaGrande" class="">A pull request has been made to back port the change, and we are currently waiting for review. While we do float some patch’s on our openssl, we do not float anything that has not received review from the team.</font></span></div><div class=""><span style="text-indent: -66.92578125px;" class=""><font face="LucidaGrande" class=""><br class=""></font></span></div><div class=""><span style="text-indent: -66.92578125px;" class=""><font face="LucidaGrande" class=""><a href="https://github.com/openssl/openssl/pull/918" class="">https://github.com/openssl/openssl/pull/918</a></font></span></div><div class=""><span style="text-indent: -66.92578125px;" class=""><font face="LucidaGrande" class=""><br class=""></font></span></div><div class=""><span style="text-indent: -66.92578125px;" class=""><font face="LucidaGrande" class="">I was curious if there is anything we can do to help expedite the process, you can see </font></span><a href="https://github.com/aws/aws-sdk-js/issues/862" class="">in this issue</a> that there are numerous individuals affected by this problem, and some of the work arounds are… less than ideal.</div><div class=""><br class=""></div><div class="">Thank you for your time and all the hard work you do on the project!</div><div class=""><br class=""></div><div class="">Best,</div><div class=""><br class=""></div><div class="">Myles Borins</div></body></html>