On zondag 12 september 2021 19:57:17 CEST Sandro Knauß wrote: > But first make sue, that you are really have an valid bug. Please verify the > signature in a konsole via gpg --verify. I expect, that it will fail with > the same error.
Thanks for your assistance. I've save the signature as 'signature.asc' and the
signed part of the email msg to 'attempt3-dos.txt'
$ gpg --verify signature.asc attempt3-dos.txt
gpg: Signature made di 31 aug 2021 16:07:34 CEST
gpg: using RSA key 92AAD901B21B4BC79A47A03054F1A66317486713
gpg: Good signature from "Joost E. van Baal (Nederland, 1970)" [full]
gpg: aka "Joost van Baal <joos...@mdcc.cx>" [full]
gpg: aka "Joost van Baal <j.e.vanb...@uvt.nl>" [full]
gpg: aka "Joost van Baal <joos...@debian.org>" [full]
gpg: aka "Joost van Baal <joos...@enosig.org>" [full]
gpg: aka "Joost van Baal <joos...@logreport.org>" [full]
gpg: aka "Joost van Baal <joos...@ad1810.com>" [full]
gpg: aka "Joost van Baal-Ilić" [full]
Primary key fingerprint: B8FA C2E2 5047 5B8C E940 A919 5793 0DAB 0B86 B067
Subkey fingerprint: 92AA D901 B21B 4BC7 9A47 A030 54F1 A663 1748 6713
Hoping/expecting to validate the message against my keyring with "gpg --verify
attempt3-dos.txt" failed as "gpg --verify" wants the signature file as first
parameter.
Let me know what else I can do.
Cheers,
Diederik
signature.asc
Description: This is a digitally signed message part.
