Legacy parser mode for Jacksum 1.7.0 with option -m generated files

[Alepod]

Please re-implement original Jacksum's 1.7.0 parsing mode with self-signed hashlists and keys like -w or -m. It was enormously useful.

[Alepod]

It could also be used by default, if using -c without -E or -a, for the sake of convenience

[Alepod]

Please keep it's behavior, when it could split files by catalogs or could have single list with relative paths.

[jonelo]

Alepod, what do you mean with "self-signed hashlists" and "when it could split file according to catalogs or could avoid that as weel." ?

[Alepod]

Alepod, what do you mean with "self-signed hashlists" and "when it could split file according to catalogs or could avoid that as weel." ?

Sorry for unclear message, comment was fixed

[jonelo]

Thanks for clarifying your request, Alepod.

Well, from the today's point of view I must admit that the Jacksum 1.7.0 check file format from 2003 has too many hurdles actually:

• 3rd party software vendors found it difficult to parse those files
• it was often saved in non-Unicode charsets which is not good for localized filenames/foldernames
• the meta information in the files have a direct relationship to the CLI which it shouldn't have
• it is cumbersome to extend the format with new features
• ...

Therefore I have removed it in Jacksum 3.

Workarounds:

• If you still have Jacksum 1.7.0 check files, I suggest to use Jacksum 1.7.0 to parse those. Jacksum 1.7.0 can still be found on sf.net/project/jacksum
• Recalculate digests with Jacksum 3+, use a modern cryptographic, non-broken hash algorithm,
  and use the Jacksum standard output format or one of the predefined standard formats (see also jacksum -h --compat).

Plans:
I understand that you (and maybe others?) like/require the old Jacksum 1.7.0 format, so I plan to add a compatibility module for Jacksum 1.7.0 files. However, since easy workarounds exist, this request has a lower prio for now.

[Alepod]

Well, if you consider JS1.7.0 format uneffective for new JS, then I suppose the new self-explanatory hash list format could be designed. Jacksum would be able to use this info if called with single param, like jacksum -c hash.jacksum. And possibility to split list by catalogs would be much appreciated, too. It looks really neat.

Perhaps I should submit new issue, right?

[jonelo]

yes, please! 😁