Minor issue/bug with ASSP_AFCKnownGoodEXE config file comments. I've got 2 sha256 entries in my ASSP_AFCKnownGoodEXE. The file looks like
# PDF from accounting Dec 2022 7B366390CD4E3DB19E06009FCE54DF272BEE0D3B34003F3A786C4835239BFDFF # PDF from IRS Dec 2022 1EBE9B7DC3AEF7F492FCD22D4430123FEEA663A3227AB9F70D59ACDCBFB06C36 When I save, I get this in the log: Dec-17-22 22:57:30 ASSP_AFCKnownGoodEXE: invalid attachment SHA256_HEX definition - hash: is ignored Dec-17-22 22:57:30 ASSP_AFCKnownGoodEXE: invalid attachment SHA256_HEX definition - hash: is ignored Dec-17-22 22:57:30 ASSP_AFCKnownGoodEXE: 2 well known good SHA256_HEX attachment hashes registered It doesn't seem like it's happy with the comment lines. If I put the comment on the same line, after the sha256, it ASSP doesn't complain 7B366390CD4E3DB19E06009FCE54DF272BEE0D3B34003F3A786C4835239BFDFF # PDF from accounting Also, I found a cosmetic mistake in the ASSP file editor GUI. The note at the bottom says: File should have one entry per line; anything on a line following a number sign ( #) is ignored (a comment). Whitespace at the beginning or end of the line is ignored. There's a space before the #.
_______________________________________________ Assp-test mailing list Assp-test@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-test
