txacme
txacme copied to clipboard
twisted
Twisted client for the ACME (Automatic Certificate Management Environment) protocol
This is necessary, rather than going directly through the `ICertificateStore` interface, because the issuing service may be in the process of reissuing the certificate, resulting in the new cert being...
The trick of creating an empty file to provision a new cert is somewhat error-prone and confusing, as evidenced by how many people stumble over it when deploying txacme; we...
The endpoint should be switched to use this method, too.
There should be a `twistd` command that runs an issuing service standalone. This would be most useful with `http-01` and `dns-01` challenge types, putting certificates into a store (eg. a...
> This lets you run some arbitrary code after something's been stored, so you can rehash nginx or whatever. This was the major blocker for me adopting txacme: some services...
http://sphinx-autoapi.readthedocs.io/ This should probably be a lot less traumatic than apidoc/autodoc.
Hi! I think it might be useful to have a tutorial which covers "here are the steps you should take as someone who wants to set up a website with...
Something like `txsni.maputils.Cache` is too simplistic, because it assumes the underlying store will never change, which is obviously false in the case of txacme.
Cryptography no longer IDNA encodes names for us, should we be doing this instead?
This is mostly dependent on SAN support (#37). We would like to be able to: 1. Issue a single certificate for multiple domains (SAN) 2. _Change_ the domains (add/remove) for...
