Is the lure of letsencrypt that<p>1 it&#x27;s accepted without warning in browsers or<p>2 it lets users ignore learning how to use the openssl binary (or writing their own tools with libssl, polarssl, etc.) to generate ca and site keys, certs, csr&#x27;s, crl&#x27;s, etc., or<p>3 both?<p>Here, the author appears to benefit mainly from 1.<p>Assuming letsencrypt does not do any sort of commercial CA-type &quot;verification&quot; then why do they need to be a CA?  Why does one need an account?<p>Answer: browsers clinging to CA system.<p>Why not just get browsers to drop the warnings for self-signed certs?<p>The goal here, I thought, is to facilitate encrypted traffic, not to give a false sense of &quot;authentication&quot;, correct?<p>Encryption and authentication are two different things.<p>Every user should understand that.