Re: [Acme] acme-scoped-dns-challenges: account hash

2024-03-16 Thread Amir Omidi
Thank you! I've made this PR to be consistent between the KIDs: https://github.com/aaomidi/draft-ietf-acme-scoped-dns-challenges/pull/41 On Sat, Mar 16, 2024 at 8:31 AM Richard Körber wrote: > Thank you! Yes, that fixed the problem. > > Looking at the specs again, I should have figured it out

Re: [Acme] acme-scoped-dns-challenges: account hash

2024-03-16 Thread Richard Körber
Thank you! Yes, that fixed the problem. Looking at the specs again, I should have figured it out myself. Thanks, again! it was "https://example.com/acme/acct/ExampleAccount; but looks like autometic line change was in bad place 2024-03-16 오후 8:19에 Richard Körber 이(가) 쓴 글: Hello! In

Re: [Acme] acme-scoped-dns-challenges: account hash

2024-03-16 Thread Seo Suchan
it was "https://example.com/acme/acct/ExampleAccount; but looks like autometic line change was in bad place 2024-03-16 오후 8:19에 Richard Körber 이(가) 쓴 글: Hello! In section 4 of draft-ietf-acme-scoped-dns-challenges-00, an example is given about how to calculate the hash of the account

[Acme] acme-scoped-dns-challenges: account hash

2024-03-16 Thread Richard Körber
Hello! In section 4 of draft-ietf-acme-scoped-dns-challenges-00, an example is given about how to calculate the hash of the account resource URL. The example gives this account URL: "https://example.com/acme/acct/; According to the example, the result of the "base32(SHA-256()[0:10])"