-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 David Shaw wrote on 26.11.2005, Сб 18:30: > On Sat, Nov 26, 2005 at 06:01:49PM +0300, lusfert wrote: >> >>When I open clearsigned 1.txt.asc I can find symbol U+FEFF (Zero width >>no-break space) before message, but after field "Hash:". Adding option >>-t does not change anything. But if source file is encoded in UTF-8 >>without BOM, character U+FEFF doesn't appear in output clearsigned text. > > > U+FEFF is the BOM character. It was in the original document, so it's > in the signed document as well. > Then why this BOM character appears in clearsigned text if option - --textmode (-t) is used? As I understand from its description in man file GnuPG threat input file as text. But BOM is a file, not text signature; then why U+FEFF appears in output text? Or I'm wrong?
PS And what about problem with verifying signatures from PGP Global Directory messages via GnuPG + Enigmail? GPG still writes: WARNING: signature digest conflict in message http://lists.gnupg.org/pipermail/gnupg-users/2005-September/027076.html I sent an example a long time ago. Regards - -- Current OpenPGP key ID: 0x500B8987 Key fingerprint: E883 045D 36FB 8CA3 8D69 9C79 9E35 3B56 500B 8987 Encrypted e-mail preferred. -----BEGIN PGP SIGNATURE----- iD8DBQFDiNEKnjU7VlALiYcRAyYiAJsHfCpU3zY6WErZYC1oGEjH6OIyBACgz92r RISSoLMi5NHYKT0mOBIS2vY= =ObRI -----END PGP SIGNATURE----- _______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
