-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 01/23/2013 08:21 AM, Alessandro Basili wrote: > On 23/01/2013 13:36, LeRoy wrote: >> enigmail> /usr/bin/gpg --charset utf8 --batch --no-tty --status-fd >> 2 --keyserver -options auto-key-retrieve --keyserver pgp.mit.edu >> --decrypt gpg: Signature made Wed 23 Jan 2013 04:37:03 AM EST using >> RSA key ID 565C4450 gpg: BAD signature from "alessandro basili >> <[email protected]>" enigmail.js: >> Enigmail.decryptMessageEnd: Error in command execution > >> I think that your problem is that you are using html to send >> messages from windows without using pgp mime. Even having pgp mime >> set for sending messages MS Windows does not always behave >> properly. > > > If you look at the message header you would see: > > Content-Type: text/plain; charset="utf-8" > > so is cannot be a problem of html. Aside from that I do not know why > should I use MIME, could you elaborate?
With Unix type systems MIME has long been a standard. With html and maybe with utf-8 the message can get changed passing through some servers thus breaking the signature. Mime encoding somehow prevents the changing of the message. I realize that MS Windows does not handle Mime encoding very nicely whereas BSD, OS X, Linux, and other Unix based systems Mime encoding is a standard. > > The problem seems somehow to be linked to charset since every time I > reply and some special characters are included (like Ludwig's > surname), then my signature fails. This message came through just fine with text/plain; charset="us-ascii" > > In the following quote from Ludwig, from which I overwrote his surname > (hope you will not get offended for that!): > >> On 21/01/2013 20:59, Ludwig ******** wrote: >>> To come back to Enigmail: Version 1.5 is suffering from bug which >>> probably made your signature invalid >>> (https://sourceforge.net/p/enigmail/bugs/106/). This bug has been >>> fixed in the latest nightly builds. > > a problem related to "special characters" is somehow explained and > declared to be fixed in version 1.5.1. > Either my problem is different or the code is still not fixed. > _______________________________________________ enigmail-users mailing list [email protected] https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net - -- Rev. LeRoy D. Cressy mailto:[email protected] /\_/\ http://lrcressy.com ( o.o ) > ^ < Cell Phone: 267-307-3527 Open PGP Key: C34B77CC gpg fingerprint: 8AD5 35EF 1FDF F1A7 E483 8CCE A50D 4E81 C34B 77CC For info on enigmail: http://enigmail.mozdev.org/ For info on gpg: http://www.gnupg.org/ Jesus saith unto him, I am the way, the truth, and the life: no man cometh unto the Father, but by me. (John 14:6) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBCgAGBQJRAH+CAAoJEI9ujBCAoueIT9YP/iNJi+1RIUUZ8nV14Y9wOsHj cxbTnTxmGAw+qkyzjlzIvKMPKfuHu+uCxiQIOOodGexxZktmQBSWU7WD74mql0tr 1oy3dpveJVFRa8BadfFPVG/V6Yvfx/jU7f4xh0sDbwV7tZzwvcNCO+mSkCW1Ortb wXyxq+Nld70YMn4YDhGhRL9cY6x8sRyqpxpk7tgYuJgsvLSHTval7nqxy0BcLrQj dpqxAK+FP/mArAxPcitJqYKofty1FNiBa2e3+4P7niSeMrezzy7X0hRGARKHKeVu 96nYIvef/3mSCyAFU0zjBvznS5145yujuOi0/Js+overfE0MEpRV5SJMgA4gV++F gueMCEMNVWygCKGxvOBiLI6UZcZUj7KPqa3Mrcj6BVNMY6FxkIR1DpfsjMawC4hy Lkdd7cl7BDxU39i/Dg+GZg7d+iEdps0Xt72QiHY3HMalm2kwCOxW9LDz6EFdGiL6 0amr6Opreq8wOYrti0oXsT5zVmATkRVC/ML5vyq/KQFT4td1YrN2Ocp1bbYcu6vs 31WOx8iuf07psKig2bBtrRSD/0WxJKy4cHNk91UULHhlNrOrcuJ9OLolUjhLGiCK Q8HVpQR8E5MKjlVPTg9HA7G7zOIQ1rNWHKF82b53brPpoW7XsG9pFwNKrzJ+hh2l dPXPP0GirsHCPR231R88 =g00z -----END PGP SIGNATURE----- _______________________________________________ enigmail-users mailing list [email protected] https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
