List view
The client is to be changed to default to API v2.0 (and potentially to DNS verification mode if the list of the domains contains wildcards). This should remove the need of specifying --api 2 --handle-as dns explicitly. Additionally the CSR handling is to be changed to account for the case of having some extra texts (such as comments) outside of the BEGIN/END block.
No due date•1/1 issues closedBoulder code is to implement authz randomisation in the newOrder request. We should support that in advance. Additionally the order and even the amount of identifiers returned is not guaranteed to match the order and amount of authorisations already, so the code change should account for that (without breaking compatibility with older protocol). Wildcards also require additional change to the client, to try www if the expiration is checked against the website and to support a specifically given URL to check the expiration against. The changes are to go in v0.32
No due date•1/1 issues closedLibrary to be made compatible with both old (v1.0) and new (v2.0) API. The processing flow should remain the same, allowing legacy code/clients to use it without changes. Wildcard support to be introduced (NB: This might be potentially breaking for the third-party code handling DNS verification, but _only_ in case of the wildcard being used, since the DNS record in that case is identical to that of a "normal" domian).
Due by March 1, 2018•1/1 issues closedA set of enhancements and fixes for windows builds.
Due by August 21, 2017•3/3 issues closedSilent mode to be added, utility functions to retrieve expiration information to become part of the library rather than client, so could be re-used from the custom client applications.
Due by June 25, 2017•1/1 issues closedIDN (internationalized domain name) support to be implemented, preferably with only core modules. Note: the library can deal with IDN just fine, as long as you pass down those names in punycode. The task is to add appropriate conversion to the client application.
Due by April 30, 2017•1/1 issues closedCrypt::OpenSSL::PKCS10 does not work on Windows. As a result, while the client can be made portable, it is currently missing the CSR generation feature on that platform. That module is to be dropped and replaced with the code that allows CSR to be created on Windows.
Due by November 14, 2016•1/1 issues closed- Due by August 22, 2016•1/1 issues closed