<div dir="ltr">I was in the closed beta and have it on a couple of my sites and services. The scripts are fully open-source, so if you're really concerned about their automated systems you can review them yourself or write your own. Very cool project overall, and a good excuse to run your sites and services through something like Qualys' SSL Server Test to make sure your HTTPS parameters are configured optimally.</div><br><div class="gmail_quote"><div dir="ltr">On Tue, Dec 8, 2015 at 3:22 PM Chris Wieringa <<a href="mailto:chris@wieringafamily.com">chris@wieringafamily.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">I ran through the process of cloning the client and retrieving a certificate for my home web server. Overall, it wasn't that much of a hassle. <div><br></div><div>The client performs a 3rd-party verification of your website / domain-name by having temporarily hosting a webserver on either port 80 or 443, or by writing into your webroot a verification file. It wrote into the .well-known/acme-challenge/ directory in my webroot for that process.</div><div><br></div><div>I get a bit annoyed with the default mantra of "we'll do everything for you" with the client wanting to reconfigure Apache automatically, but it's simple enough to skip that then modify my Apache config for the certificates manually. Likewise, it looks like CSRs can be sent as well if you want to do that manually.</div><div><br></div><div>Since they issue 90 day certificates, it seems like using the client and a cron entry seems like the easiest way to keep this working long-term.</div></div><div dir="ltr"><div><br></div><div>Chris</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Dec 8, 2015 at 1:06 PM, Thomas Wodarek <span dir="ltr"><<a href="mailto:kc8zpq@gmail.com" target="_blank">kc8zpq@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">There has been discussion on the LE dev list about web UIs ( <a href="https://groups.google.com/a/letsencrypt.org/d/msgid/client-dev/CA%2B65OsrZSyX0DpGn5CsrOVbz6TUWv7x9EWdOV9wMoHoDn8oRcg%40mail.gmail.com" target="_blank">https://groups.google.com/a/letsencrypt.org/d/msgid/client-dev/CA%2B65OsrZSyX0DpGn5CsrOVbz6TUWv7x9EWdOV9wMoHoDn8oRcg%40mail.gmail.com</a>), the latest of which is <a href="https://gethttpsforfree.com" target="_blank">https://gethttpsforfree.com</a>.</p>
<p dir="ltr">The installed client part is to allow automation, which is pretty much the reason behind the LE project.</p><div><div>
<div style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Is there a way to have a cert issued like any other authority by just submitting a CSR and getting the cert back? And not having to install some special "software" ?</div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Dec 8, 2015 at 12:28 PM, L. V. Lammert <span dir="ltr"><<a href="mailto:lvl@omnitec.net" target="_blank">lvl@omnitec.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
Public Beta is available as of 3 December:<br>
<br>
<a href="https://letsencrypt.org/2015/12/03/entering-public-beta.html" rel="noreferrer" target="_blank">https://letsencrypt.org/2015/12/03/entering-public-beta.html</a><br>
<br>
Has anyone implement yet?<br>
<br>
Lee<br>
_______________________________________________<br>
grlug mailing list<br>
<a href="mailto:grlug@grlug.org" target="_blank">grlug@grlug.org</a><br>
<a href="http://shinobu.grlug.org/cgi-bin/mailman/listinfo/grlug" rel="noreferrer" target="_blank">http://shinobu.grlug.org/cgi-bin/mailman/listinfo/grlug</a></blockquote></div><br></div>
<br>_______________________________________________<br>
grlug mailing list<br>
<a href="mailto:grlug@grlug.org" target="_blank">grlug@grlug.org</a><br>
<a href="http://shinobu.grlug.org/cgi-bin/mailman/listinfo/grlug" rel="noreferrer" target="_blank">http://shinobu.grlug.org/cgi-bin/mailman/listinfo/grlug</a><br></div>
</div></div><br>_______________________________________________<br>
grlug mailing list<br>
<a href="mailto:grlug@grlug.org" target="_blank">grlug@grlug.org</a><br>
<a href="http://shinobu.grlug.org/cgi-bin/mailman/listinfo/grlug" rel="noreferrer" target="_blank">http://shinobu.grlug.org/cgi-bin/mailman/listinfo/grlug</a><br></blockquote></div><br></div>
_______________________________________________<br>
grlug mailing list<br>
<a href="mailto:grlug@grlug.org" target="_blank">grlug@grlug.org</a><br>
<a href="http://shinobu.grlug.org/cgi-bin/mailman/listinfo/grlug" rel="noreferrer" target="_blank">http://shinobu.grlug.org/cgi-bin/mailman/listinfo/grlug</a></blockquote></div>