suspicious ntpleapfetch checksum error

[Martin Boissonneault]

Hi Steven, all,

Thanks for opening the issue and providing a workaround. I'll drop in on the issue when I can for follow-up.

Martin Boissonneault
Sent from my phone

> On May 6, 2020, at 06:18, Steven Dodd via users <users at ntpsec.org> wrote:
> 
> I get the same (even with the script from master).
> 
> This line in the ntpleapfetch script:
> 
> local FSHA1="`grep '^#h' $1 | tr -d '[:cntrl:]' | sed -e's/^#h//' -e's/ / 0x/g'`"
> 
> Doesn't prepend the first segment of the provided hash with 0x hence the error:
> 
> 
>> The odd part is the //usr/local/bin/ntpleapfetch: 1: printf: a1c168ae: expected numeric value/ part, and the /a1c168ae/ part is the part later shown as zeroes in the expected checksum part. The checksum, with that part substituted, is what is computed.
>> Any idea? I'm using NTPsec 1.1.8 compiled from the release tarball on the current Raspbian Buster for the Raspberry Pi 3B+.
> 
> Putting:
> 
> local FSHA1="`grep '^#h' $1 | tr -d '[:cntrl:]' | sed -e's/^#h/0x/' -e's/ / 0x/g'`"
> 
> (so substituting the #h with 0x instead of just removing it) fixes it for me.
> 
> This may or may not be the right answer.
> 
> I opened a gitlab issue with this information.
> 
> -Steve.
> _______________________________________________
> users mailing list
> users at ntpsec.org
> http://lists.ntpsec.org/mailman/listinfo/users