Re: [trinity-users] Trinity SSL Certificates

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA224 What I personally don't care for from Lets Encrypt is the short expiry time effectively requiring automated install. Whenever you have automated install from a third party onto a local machine this is generally an opening for security problems at some point down the line -- I have yet to see a system without a human in the loop where this has not happened. If Let's Encrypt wasn't pushing their own tools in lieu of the relatively standard methods for setting up SSL encryption, and provided a more reasonable expiry time, they would be far more attractive. As it stands, one could easily run into a worst case scenario with nearly expired certs that Lets Encrypt refuses to or cannot renew, and that's a risk that is very hard to accept. Finally, while not directly applicable to TDE, Lets Encrypt still does not support wildcard certificates. This would make e.g. logins to QuickBuild impossible without significant technical changes, sucking time away from TDE itself onto the tools required to control modern cloud services.