-
From RFC8555 [section 6.7 ](https://tools.ietf.org/html/rfc8555#section-6.7):
> When the server responds with an error status, it SHOULD provide additional information using a problem document [[RF…
-
I've been looking at Let's Encrypt logs, and I notice a number of entries that just have User-Agent: curl/x.y.z. It looks like getssl doesn't currently set this header explicitly. It would be really h…
-
While doing some testing for the upcoming POST-as-GET changes, I noticed that [RFC8555 Section 6.3](https://tools.ietf.org/html/rfc8555#section-6.3) states that,
> The server MUST allow GET request…
-
I am not sure if it is a bug of win-acme or of my acme-server. What do you mean?
```
C:\acme-clients\win-acme.v2.1.5.742.x64.pluggable>wacs.exe --verbose
[VERB] Verbose mode logging enabled
[V…
-
ACMEs RFC (https://tools.ietf.org/html/rfc8555#section-6.3 and following) defines some of the requests to be POST-as-GET.
We do not adhere to that everywhere and have to adjust to be compliant.
Th…
-
There is cases when payload is empty string in JWS JSON token (for example in `ACME` protocol: https://tools.ietf.org/html/rfc8555#section-7.4.2), but `Crypt::JWT` return `unsupported JWS/JWT JSON Ser…
-
While testing my OS Java ACME server impl I came across the topic of expected 'id' element in the account response. As far as I can see there is nothing like this included in the spec.
My proposal wo…
-
I would like to configure the (m)TLS settings on a per path prefix basis.
This would allow supporting domain based protocols like ACME used by lets-encrypt [RFC8555](https://tools.ietf.org/html/rfc…
-
Since Acme has now released as [RFC8555](https://tools.ietf.org/html/rfc8555), this Client should be updated to remove the usages of GET-Requests where the [POST-AS-GET](https://tools.ietf.org/html/rf…
-
Given a CSR which only has the `CN` field set without any `subjectAltName`, pebble returns `Order includes different number of names than CSR specifies`. This is likely because the check
in [Finaliz…