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 <ac...@ml.shredzone.de>
wrote:

> 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 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(<ACCOUNT_RESOURCE_URL>)[0:10])" operation is supposed
> >> to be "ujmmovf2vn55tgye".
> >>
> >> However, in my implementation I get the hash "jkk3cewh6vmq7rgf".
> >>
> >> I checked my code multiple times, but could not find an implementation
> >> error.
> >>
> >> Before I am going to waste more time with debugging, I'd like to ask
> >> if the example result in the specs is correct?
> >>
> >> Thank you!
> >>
> >> Best,
> >> Richard Koerber
> >>
> >> _______________________________________________
> >> Acme mailing list
> >> Acme@ietf.org
> >> https://www.ietf.org/mailman/listinfo/acme
> >
> > _______________________________________________
> > Acme mailing list
> > Acme@ietf.org
> > https://www.ietf.org/mailman/listinfo/acme
>
> _______________________________________________
> Acme mailing list
> Acme@ietf.org
> https://www.ietf.org/mailman/listinfo/acme
>
_______________________________________________
Acme mailing list
Acme@ietf.org
https://www.ietf.org/mailman/listinfo/acme

Reply via email to