<html><head></head><body><div style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:16px;"><div style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:16px;"><br>n Tuesday, September 12, 2017, 9:39:32 AM GMT-6, Pete Wright <pete@nomadlogic.org> wrote: <br><br><br><br>On 09/12/2017 07:38, Michael W. Lucas wrote:<br>> On Tue, Sep 12, 2017 at 02:24:00PM +0000, George Rosamond wrote:<br>>> Mark Saad:<br>>>> All<br>>>> I was looking tat replace a wildcard ssl cert on a commercial site and I was looking for options .<br>>>><br>>> wildcard certs have security implications to them. Best to avoid.<br>>><br>><br>> Out of curiosity: any real-world reason not to do Let's Encrypt?<br><div>></div><div><br></div><div>This is a commercial setup, from what I remember LE is for non-commercial setups. </div><div>Also I need to get two wild cards one for *.mydomain.xxx and *.yyy.mydomain.xxx<br></div><div>and I dont think LE can do the latter. <br></div><div><br></div><div>> I'm pondering writing a book on LE with acme.sh.<br></div>i'd be keen to get a copy of that! the devs i support loved your ssh <br>book, and i loved it b/c i didn't have to actually interact with humans :)<br><br>one issue i've had with let's encrypt is trying to use it on private <br>subdomains on AWS. iirc the system needs to have a public DNS entry as <br>well as access from the internet to work - i might be mistaken tho on <br>this...<br><br>-pete<br><br>-- <br>Pete Wright<br>pete@nomadlogic.org<br>@nomadlogicLA<br><br><div><br></div><div>-- Mark Saad | mark.saad@ymail.com<br></div><div><br></div>_______________________________________________<br>talk mailing list<br>talk@lists.nycbug.org<br>http://lists.nycbug.org/mailman/listinfo/talk<br><br></div></div></body></html>