Support IP address identifiers about pebble HOT 9 CLOSED

@orangepizza why not create a PR for this here and mark it as WIP? That way it is easier for others to look at and comment your code.

I can try your code out with my client; I've added experimental support for IP identifiers a couple of days ago, then we can see whether/how it works.

from pebble.

IP identifiers are supported (and at least unit tested) by my client, too. I could give it a try as well.

from pebble.

I could successfully create an IP based certificate via http-01 using acme4j. 👍

from pebble.

Sorry, took me a bit longer to really try this out. I've now managed to get a certificate for a IPv4 address (127.0.0.1) and a IPv6 address (::1) issued!

(WIP PR for Ansible's ACME client: ansible/ansible#53228, PR for my test environment to work with orangepizza's branch and adds IP tests: felixfontein/ansible-acme-test#1)

from pebble.

I made I_think_this_works version, can't find client that support pebble and easy enough to mass with
it's compiled and tested for signs cert wih normal domains, and I checked WFE parts with modified client, but couldn't make the clients work with actual CSR with IP Address. , but when csr passed with shortcut (with some hack), it will sign it properlly
from checklists:
pebble.zip

TLS-ALPN-01 doesn't implanted yet

from pebble.

PR is in #221.

from pebble.

Thanks everyone! It would certainly be useful to hear about any interop testing you folks manage to do. Please share your experience in this thread.

from pebble.

I've now also managed to get a certificate for 127.0.0.1 with TLS-ALPN-01 validation! \o/

(I can't get one for ::1 since apparently Python's socketserver doesn't work for IPv6...)

from pebble.

Implemented in bc4da68 thanks to @orangepizza 🎉 🥂

from pebble.