signify: unable to parse checksum error.

[jjstorm]

I want to keep track of the hashes of config files that I am saving for future use. Below is an example of what I am referring to.

untrusted comment: verify with mykey.pub
RWQK3BH3tqw7m29hdaNZGozCOj+kxqr6Z405Dxn8/K9garTmXpPbucJGFib0wB/z1V40QNpDhAzpr8nu5cQUSyoo18sGJGK/HAE=
SHA256 (mixerctl.conf.cfg) = bafc3c2ecc10fb26cdc0534c159465d1bc25fac3b17c13648ab8679be05384c4
SHA256 (xfce_4.1.2p.cfg) = de5dd202811c8e2ec334c31750111cde1e047fb574dcbcafc8bb14457e2d79ec

The above file is the result of copying and pasting the checksums output for the two files to a text file, and then signing it with the signify key using the -e option.

How I signed the above file:

$ signify -S -e -s mykey.sec -m SHA256 -x SHA256.sig

Below is the error I get when I try to verify the signatures.

$ signify -C -p mykey.pub -x SHA256.sig xfce_4.1.2p.cfg
Signature Verified
signify: unable to parse checksum line 
$

UPDATE:

The above error is no longer. Instead the file checks OK.

The exact above process worked after recreating it using a graphical text editor, rather than vi.
A hidden character could have been pasted into vi that caused signify to throw an error.

[jggimi]

Don't edit signed files.

[ocicat]

Originally Posted by jjstorm

I want to keep track of the hashes of config files that I am saving for future use.

You may also want to look at mtree(8). It is designed exactly for this purpose.