On 07/11/2017 06:23, William Atwood wrote:
> Michael,
>
> My point is not in how the hash is used, but that the example is wrong.
Yes. The value has been there since draft -08 and it's been wrong all along.
> Neither sha1sum nor sha256sum gives "a379a6f6ee" as the first 40 bits.
Nor does MD5, which was specified in earlier versions of the draft.
(The text makes it clear that it's the raw name that is hashed, so including
LF, CR or both would be wrong.)
Brian
>
> poise bill > echo -n area51.research.acp.example.com | sha1sum
> 78145a90f86c6a7c7a92605b67a5d9373bde0fae -
>
> Therefore, since neither my sha256sum result nor my sha1sum result is
> the same as the example, and since you have verified that my sha256sum
> result is correct (and the draft calls for a sha256sum result), the
> result in the example is wrong, and needs to be corrected.
>
> Bill
>
> On 06/11/2017 10:57 AM, Michael Richardson wrote:
>>
>> William Atwood <[email protected]> wrote:
>> > For two different on-line generators, I get the following results:
>>
>>
>>
>> > http://www.xorbin.com/tools/sha256-hash-calculator
>> > area51.research.acp.example.com
>> > 89b714f3db8e41558cfb49d4d763ee7cc5ae53a3ffe8a17039679d06dc9bb0e3
>>
>> Sometimes the difference is whether or not a CR and/or LF is included in the
>> hash. I see that your result is without the line feed.
>>
>> dooku-[~](2.3.0) mcr 14553 %echo area51.research.acp.example.com | sha256sum
>> 60b1547f399cb8354010e0bd5853f0bcd393590e44efa2cb47c233615e9ce766 -
>> dooku-[~](2.3.0) mcr 14554 %echo -n area51.research.acp.example.com |
>> sha256sum
>> 89b714f3db8e41558cfb49d4d763ee7cc5ae53a3ffe8a17039679d06dc9bb0e3 -
>>
>>
>>
>> But, the only device that needs to create the ULA prefix is the registrar
>> during it's bootstrap, and once created it is to be stored. I would expect
>> that if there was an administrator interface that it would ask for some
>> domain details, and then pre-populate a "ACP prefix" field with the result,
>> but let the admin type in their own.
>>
>
_______________________________________________
Anima mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/anima
