On 4/24/19 4:15 PM, Florian Obser wrote:
> On Wed, Apr 24, 2019 at 09:34:57AM -0400, Bryan Steele wrote:
>> On Wed, Apr 24, 2019 at 03:08:59PM +0200, Fabio Scotoni wrote:
>>> [...]
>>
>> Isn't RF C8555 ACMEv2? acme-client(1) only supports ACMEv1, so I don't
>> think this is correct.
>>
>
>
On Wed, Apr 24, 2019 at 09:34:57AM -0400, Bryan Steele wrote:
> On Wed, Apr 24, 2019 at 03:08:59PM +0200, Fabio Scotoni wrote:
> > This diff updates the acme-client(1) STANDARDS section.
> > Currently, it lists an RFC draft for the ACME protocol.
> > Since March of this year, there is a proposed
On Wed, Apr 24, 2019 at 03:08:59PM +0200, Fabio Scotoni wrote:
> This diff updates the acme-client(1) STANDARDS section.
> Currently, it lists an RFC draft for the ACME protocol.
> Since March of this year, there is a proposed standard with an actual
> RFC number.
>
> While at it, make the format
This diff updates the acme-client(1) STANDARDS section.
Currently, it lists an RFC draft for the ACME protocol.
Since March of this year, there is a proposed standard with an actual
RFC number.
While at it, make the format match ssh(1) STANDARDS by providing .%A and
.%D entries.
Index: