News for hackers. Stuff that matters.
Re:Let's Encrypt Developer Preview by notatoad on Friday January 16, 2015 @06:45PM (#8902533)
The tool shouldn't need root access to /etc/nfinx (or whatever your config Dir of choice is) to authenticate your ownership of a domain.
Re:Let's Encrypt Developer Preview by thristian on Friday January 16, 2015 @07:38PM (#8902758)
The tool doesn't care about your ownership of the domain, it cares about whether the host it's running on is trusted by the owner of the domain. The simplest way to verify that is for the CA to tell the tool "serve up this nonce value at this randomly-generated URL", and then to request that URL and see if it gets the right value.

Depending on exactly what proof the CA wants, that will probably require some kind of tinkering with the webserver's config, or at least inspecting it to figure out how to fulfil the CA's request.

Hopefully there'll be a fallback mechanism that tells the sysad what to configure, if only because not every webserver in the world is Apache or nginx.

Re:Let's Encrypt Developer Preview by IgorPartola on Friday January 16, 2015 @09:01PM (#8903008)
Unless the tool includes a server that can do this all on an alternative port.
Re:Let's Encrypt Developer Preview by pas on Saturday January 17, 2015 @06:24AM (#8904112)
They explicitly want to test 443.
Re:Let's Encrypt Developer Preview by xorcist on Saturday January 17, 2015 @04:18AM (#8903950)
Or, we could just let registrars issue these certs.

Problem solved.

Re:Let's Encrypt Developer Preview by vertex-four on Saturday January 17, 2015 @06:24AM (#8904109)
They were never going to for free - the ones that do sell certs make huge amounts of money off them. That's why LetsEncrypt exists - to push the market value of a trusted X.509 certificate close to 0.