GNU bug report logs - #64390
cksum: cannot --check untagged sums file

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Christoph Anton Mitterer <calestyo <at> scientia.org>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#64390: closed (cksum: cannot --check untagged sums file)
Date: Sat, 01 Jul 2023 13:38:02 +0000

[Message part 1 (text/plain, inline)]

Your message dated Sat, 01 Jul 2023 15:37:17 +0200
with message-id <79b32ffae0d168947649c2c09e8a1a307e37ed48.camel <at> scientia.org>
and subject line Re: bug#64390: cksum: cannot --check untagged sums file
has caused the debbugs.gnu.org bug report #64390,
regarding cksum: cannot --check untagged sums file
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
64390: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=64390
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Christoph Anton Mitterer <calestyo <at> scientia.org>
To: bug-coreutils <at> gnu.org
Subject: cksum: cannot --check untagged sums file
Date: Sat, 01 Jul 2023 02:00:11 +0200

Hey.

At least as of 9.1 (on Debian), it seems that cksum cannot --check a
sums file in the untagged style:

$ touch a b
$ cksum -a sha512 --tag * > sums.tagged
$ cksum -a sha512 --untagged * > sums.untagged

$ cat sums.tagged 
SHA512 (a) = cf83e1357eefb8bdf1542850d66d8007d620e4050b5715dc83f4a921d36ce9ce47d0d13c5d85f2b0ff8318d2877eec2f63b931bd47417a81a538327af927da3e
SHA512 (b) = cf83e1357eefb8bdf1542850d66d8007d620e4050b5715dc83f4a921d36ce9ce47d0d13c5d85f2b0ff8318d2877eec2f63b931bd47417a81a538327af927da3e
$ cat sums.untagged 
cf83e1357eefb8bdf1542850d66d8007d620e4050b5715dc83f4a921d36ce9ce47d0d13c5d85f2b0ff8318d2877eec2f63b931bd47417a81a538327af927da3e  a
cf83e1357eefb8bdf1542850d66d8007d620e4050b5715dc83f4a921d36ce9ce47d0d13c5d85f2b0ff8318d2877eec2f63b931bd47417a81a538327af927da3e  b
3423932033d74d924ebe77f281d9694b1fa98103ed38b4634a06759c08b63a4fd96783dfaae8e1acedc53e36129d461a5757ccf3903f5bf64242cd78d305c473  sums.tagged

$ cksum -c sums.tagged 
a: OK
b: OK

$ cksum -c sums.untagged 
cksum: sums.untagged: no properly formatted checksum lines found
$ cksum -c sums.untagged --tag
cksum: sums.untagged: no properly formatted checksum lines found
$ cksum -c sums.untagged --untagged
cksum: sums.untagged: no properly formatted checksum lines found
$ 


Not sure whether it should try to auto-determine the format...
I guess it would be possible, as long as no algorithm name every uses
a-zA-Z0-9 as starting letter.
But I rather tend to think it would be a bad idea to do so.

However, it should be possibl to use --tag or --untagged to specify a
format.


Thanks,
Chris.

[Message part 3 (message/rfc822, inline)]

From: Christoph Anton Mitterer <calestyo <at> scientia.org>
To: Andreas Schwab <schwab <at> linux-m68k.org>
Cc: 64390-done <at> debbugs.gnu.org
Subject: Re: bug#64390: cksum: cannot --check untagged sums file
Date: Sat, 01 Jul 2023 15:37:17 +0200

On Sat, 2023-07-01 at 09:05 +0200, Andreas Schwab wrote:
> $ cksum -a sha512 -c sums.untagged

Haha... I'm so dumb. ^^
Thanks for pointing to the obvious.


Thus closing.

Cheers,
Chris.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.