<p dir="ltr">It now means that the entire web can move to HTTPS by default and there are no excuses for not having an HTTPS certificate any longer. Eg. When you type <a href="http://www.whateversite.com">www.whateversite.com</a> into your browser, by default, an HTTPS connection can be made instead. Unencrypted HTTP can die now. The issue of backdoors in Certificate Authorities still exists though, because nation state laws permit gov to obtain CA private keys and perform intermediation. Therefore, we also need to ensure public key pinning and validation of per-site certificates in order to identify rogue site certificates being generated that were not issued by the site itself. Stay safe! :)</p>
<div class="gmail_quote">On Dec 4, 2015 8:40 AM, "Charisse Castagnoli" <<a href="mailto:charisse@charissec.com">charisse@charissec.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Because there are many smart people on this list, I ask how would you evaluate this just released tool:<br>
<br>
<a href="https://letsencrypt.org/" rel="noreferrer" target="_blank">https://letsencrypt.org/</a><br>
<br>
I'm too old to read source code and cert/key gen is specialized knowledge in any case.<br>
<br>
Comments?<br>
<br>
charisse<br>
_______________________________________________<br>
Dailydave mailing list<br>
<a href="mailto:Dailydave@lists.immunityinc.com">Dailydave@lists.immunityinc.com</a><br>
<a href="https://lists.immunityinc.com/mailman/listinfo/dailydave" rel="noreferrer" target="_blank">https://lists.immunityinc.com/mailman/listinfo/dailydave</a><br>
</blockquote></div>