[SFS] MatterMost is encrypted!

Aaron Brown aayore@gmail.com
Mon, 23 Jan 2017 15:11:50 -0700


This is a multi-part message in MIME format.
--------------050204040604090908030900
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Unfortunately, it does not.  But since it's free and automated, you can 
get a cert for each individual service.

> David L. Willson <mailto:DLWillson@TheGeek.NU>
> January 23, 2017 at 3:03 PM
> Does Let's Encrypt do wildcards? Maybe I should have used it after all.
>
>
>
> Sent from my Verizon, Samsung Galaxy smartphone
>
>
> -------- Original message --------
> From: Aaron Brown <aayore@gmail.com>
> Date: 1/23/17 14:55 (GMT-07:00)
> To: "Scelza, Jeffrey B" <Jeffrey.Scelza@charter.com>
> Cc: "David L. Willson" <DLWillson@thegeek.nu>, sfs <sfs@thegeek.nu>, 
> "David L. Willson" <dlwillson@sofree.us>
> Subject: Re: [SFS] MatterMost is encrypted!
>
> I thought Let's Encrypt was still called Let's Encrypt, and CertBot is 
> just a client to perform the automation for you.  Either way, I agree 
> that it's really easy once you get it set up.  Lower ongoing 
> administrative burden and all that.
>
> A note about Symantec:
> http://arstechnica.com/security/2017/01/already-on-probation-symantec-issues-more-illegit-https-certificates/
>
> I haven't had any trouble with browsers trusting Let's Encrypt certs.
> https://letsencrypt.org/docs/certificate-compatibility/
> Since Mozilla, Chrome, Facebook, etc. are all major sponsors, it seems 
> like they're pretty well-established at this point.
>
>


--------------050204040604090908030900
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html><head>
<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
</head><body bgcolor="#FFFFFF" text="#000000">Unfortunately, it does 
not.&nbsp; But since it's free and automated, you can get a cert for each 
individual service.<br>
<span>

</span><br>
<blockquote style="border: 0px none;" 
cite="mid:hkvuj3014dlx5htxa0lusvbe.1485208937866@email.android.com" 
type="cite">
  <div style="margin:30px 25px 10px 25px;" class="__pbConvHr"><div 
style="width:100%;border-top:1px solid #EDEEF0;padding-top:5px">   <div 
style="display:inline-block;white-space:nowrap;vertical-align:middle;width:49%;">
   	<a moz-do-not-send="true" href="mailto:DLWillson@TheGeek.NU" 
style="color:#737F92 
!important;padding-right:6px;font-weight:bold;text-decoration:none 
!important;">David L. Willson</a></div>   <div 
style="display:inline-block;white-space:nowrap;vertical-align:middle;width:48%;text-align:
 right;">     <font color="#9FA2A5"><span style="padding-left:6px">January
 23, 2017 at 3:03 PM</span></font></div>    </div></div>
  <div style="color:#888888;margin-left:24px;margin-right:24px;" 
__pbrmquotes="true" class="__pbConvBody"><meta content="text/html; 
charset=ISO-8859-1" http-equiv="Content-Type">
    
<div>Does Let's Encrypt do wildcards? Maybe I should have used it after 
all.</div><div><br></div><div><br></div><div><br></div><div 
id="composer_signature"><div dir="auto" 
style="font-size:88%;color:#364f67">Sent from my Verizon, Samsung Galaxy
 smartphone</div></div><br><br>-------- Original message --------<br>From:
 Aaron Brown <a class="moz-txt-link-rfc2396E" href="mailto:aayore@gmail.com">&lt;aayore@gmail.com&gt;</a> <br>Date: 1/23/17  14:55  
(GMT-07:00) <br>To: "Scelza, Jeffrey B" 
<a class="moz-txt-link-rfc2396E" href="mailto:Jeffrey.Scelza@charter.com">&lt;Jeffrey.Scelza@charter.com&gt;</a> <br>Cc: "David L. Willson" 
<a class="moz-txt-link-rfc2396E" href="mailto:DLWillson@thegeek.nu">&lt;DLWillson@thegeek.nu&gt;</a>, sfs <a class="moz-txt-link-rfc2396E" href="mailto:sfs@thegeek.nu">&lt;sfs@thegeek.nu&gt;</a>, "David L. 
Willson" <a class="moz-txt-link-rfc2396E" href="mailto:dlwillson@sofree.us">&lt;dlwillson@sofree.us&gt;</a> <br>Subject: Re: [SFS] MatterMost 
is encrypted! <br><br>I thought Let's Encrypt 
was still called Let's Encrypt, and CertBot is just a client to perform 
the automation for you.&nbsp; Either way, I agree that it's really easy once 
you get it set up.&nbsp; Lower ongoing administrative burden and all that.<br>
<br>
A note about Symantec:<br>
<a moz-do-not-send="true" 
href="http://arstechnica.com/security/2017/01/already-on-probation-symantec-issues-more-illegit-https-certificates/"
 class="moz-txt-link-freetext">http://arstechnica.com/security/2017/01/already-on-probation-symantec-issues-more-illegit-https-certificates/</a><br>
<br>
I haven't had any trouble with browsers trusting Let's Encrypt certs.<br>
<a moz-do-not-send="true" 
href="https://letsencrypt.org/docs/certificate-compatibility/" 
class="moz-txt-link-freetext">https://letsencrypt.org/docs/certificate-compatibility/</a><br>
Since Mozilla, Chrome, Facebook, etc. are all major sponsors, it seems 
like they're pretty well-established at this point.<br>
<span>

</span><br>

<br>
  </div>
</blockquote>
<br>
</body></html>

--------------050204040604090908030900--