<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div><blockquote type="cite" class=""><div class="">On Nov 19, 2014, at 7:08 AM, Jaime <<a href="mailto:jaime@snowmoon.com" class="">jaime@snowmoon.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">Another thought just came to me. Given recent vulnerabilities in SSL, I thought of TLS support. I haven't researched TLS for HTTPS yet. Does it also require a certificate with a third party, or can it be used more like SSH? In other words, is there a way to encrypt traffic to your website without having to buy a cert or have end users deal with a warning?</span><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""></div></blockquote></div><br class=""><div class="">While it is called SSL, the majority of your Connections are actually running over TLS (normally this is negotiated between client and server), and they still use the certs. so you either pay for someone that already has their cert trusted by the software you are using to connect. or you get your users to install your cert.. </div><div class=""><br class=""></div><div class="">-Patrick</div><div class=""><br class=""></div></body></html>