Plans, Roadmaps, Dreams, ...

Current branches ready for testing & comments

(updated mid-June 2020)

Withdrawn experiments

smart-nonces was dropped in order to get the more foundational requests wrappers in place. Now that RFC8555 support is merged, this would be another easy step...

Proposals and experimental changes

Beyond smart-nonces - As I understand it, requests always creates a new HTTP connection to LE for every step. If LE (or other ACME providers) support it (Q: do they?), the request wrapper that's part of smart-nonces should make it easy to use a persistent connection. The requests documentation seems sketchy about the details of connections - do they have to be manually reconnected if the host drops/times out?

Enable real testing with pebble It's hard to test the protocol implementation without using a working ACME server. For obvious reasons, LE doesn't want every ACME client's CI system hitting their servers, and strongly suggest using pebble for testing. The goal is to allow sewer's testing to move to running actual protocol exchanges instead of mocking all the important bits. _This is half working in a local branch. It was going along so smoothly, then it crashed hard at the validation stage, apparently because they've disabled the option that let pebble use their challtestsrv for just this sort of testing. Or - suggested in a bug discussion - it can still be made to work in just the right container setup? Arrrgh!

Provider catalog This will replace the import farms that clutter two init files, replace the ad-hoc copy'n'paste'n'modify stanza in cli for each provider, and maybe a couple other things while we're at it. This will be a somewhat breaking change, as part of fixing so many DRY violations is forcing a normalize relationship between the naming of parameters in envvars and the drivers' init methods. But that's a required enabler for getting rid of all that ad-hoc madness.