Re: Using the not-dash-escaped option
On Wed, 1 Feb 2012 21:47, expires2...@rocketmail.com said: I'm not sure that helps me. See below. - --=20\n :-) Sure it does not work if you use Content-Transfer-Encoding: 7bit Salam-Shalom, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Using the not-dash-escaped option
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi On Thursday 2 February 2012 at 9:50:34 AM, in mid:874nv9va1h@vigenere.g10code.de, Werner Koch wrote: Sure it does not work if you use Content-Transfer-Encoding: 7bit The message body looks exactly the same in the copy in my sentbox, where the header you cite above says Content-Transfer-Encoding: quoted-printable - -- Best regards MFPAmailto:expires2...@rocketmail.com No man ever listened himself out of a job -BEGIN PGP SIGNATURE- iQCVAwUBTyr2CqipC46tDG5pAQqoUgQAkQMH7/1F2815sAMvRiyKU8CCDAueiIBF EtpczAEOVBVT9EJIBNe96ByQZO0iLKWSEDbAecIraV+k6sWipK1Q6wZc307XacYL bjFgN4PyOQi0C/NEKhslcEcV5aefXqfQi0tFaQixnmbTZm52HGzIo0yvHD4lV9vb c0YdiuOC+nk= =rDAl -END PGP SIGNATURE- ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Using the not-dash-escaped option
On Thu, Feb 02, 2012 at 08:45:56PM +, MFPA wrote: On Thursday 2 February 2012 at 9:50:34 AM, in mid:874nv9va1h@vigenere.g10code.de, Werner Koch wrote: Sure it does not work if you use Content-Transfer-Encoding: 7bit The message body looks exactly the same in the copy in my sentbox, where the header you cite above says Content-Transfer-Encoding: quoted-printable I think what Werner is saying is to use quoted-printable encoding; then, the space will be represented as =20 (when encoded) and it will be less likely to get eaten by hungry mail-handling tools. -- brian m. carlson / brian with sandals: Houston, Texas, US +1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187 signature.asc Description: Digital signature ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Using the not-dash-escaped option
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi On Thursday 2 February 2012 at 9:53:00 PM, in mid:20120202215300.ga6...@crustytoothpaste.ath.cx, brian m. carlson wrote: I think what Werner is saying is to use quoted-printable encoding; then, the space will be represented as =20 (when encoded) and it will be less likely to get eaten by hungry mail-handling tools. I already had/have the option set in my MUA for Transfer-encoding for non-ascii characters in message text set to quoted-printable. The other options are no encoding or base64. - -- Best regards MFPAmailto:expires2...@rocketmail.com To know what we know, and know what we do not know, is wisdom. -BEGIN PGP SIGNATURE- iQCVAwUBTysmnqipC46tDG5pAQqvoAP+JuEkMhULPJang8TV88X/Wd8m4EFLPEEn vKBddYQURsbn4gEOQGF3frjzivJwu1e2xyaTmjDPL5GqP/ON/8irRvkxukbG/7Yz /vO67pigAYdsanSApSHOSNPZkde57vP4zf0d9wRz9LJN04ZffkYkGUHXA4rx/ZQv oHT1jSx772A= =Dsq8 -END PGP SIGNATURE- ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Using the not-dash-escaped option
On Tue, 31 Jan 2012 23:29, paul.hart...@gmail.com said: It's still missing the trailing space, assuming you put one there in the first place... many people don't realize it's supposed to be there. The best way to make sure that it does not get removed is by using QP encoding. (--=20\n). Shalom-Salam, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Using the not-dash-escaped option
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi On Wednesday 1 February 2012 at 5:20:46 AM, in mid:ui@r78.nl, Remco Rijnders wrote: And for what it's worth... my client tells me the signature on this particular post you made is invalid. Your other posts to this list all pass the test ;-) I just tried and got good signature. Strange. - -- Best regards MFPAmailto:expires2...@rocketmail.com Two wrongs don't make a right. But three lefts do. -BEGIN PGP SIGNATURE- iQCVAwUBTymec6ipC46tDG5pAQocLAP+IaLSzxKmMBpFvwsjR9a/plg6LLOWp/N9 8rv6rxCkHaKYfJCv0SjBuZPmuGNwn0TAhre9KwhMoL7DISBd6qTnsv0xewlSEo0W uQl6MSj+8dFLLxDp8w6j1/3oTo/Lg03UKrK9nHIKDY5T9BGeZxdCipPaHxOiaupb EIfiKbW+Ju0= =O/Ew -END PGP SIGNATURE- ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Using the not-dash-escaped option
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi On Wednesday 1 February 2012 at 8:48:53 AM, in mid:87ehuf0wi2@vigenere.g10code.de, Werner Koch wrote: The best way to make sure that it does not get removed is by using QP encoding. (--=20\n). I'm not sure that helps me. See below. - --=20\n Best regards MFPAmailto:expires2...@rocketmail.com Put knot yore trust inn spel chequers -BEGIN PGP SIGNATURE- iQCVAwUBTymk0KipC46tDG5pAQoqdwP8CPzC5lzhYYpTkOIEeWIqPVCTKH57Wg84 ZFeZgXKXfWDnXRVVVoSQkzzDfrpA7m+AbITeWPRZR+368tI0U4VHtigWsnAyRT+1 km7DhdpzWgke+qNY4yxMF/uJG+JQMUg+6QvbhRYNmBBeKokjh6liSlIu3DXeH8w+ rpHDadHFFiE= =MW47 -END PGP SIGNATURE- ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Using the not-dash-escaped option
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 NotDashEscaped: You need GnuPG to verify this message Hi On Monday 30 January 2012 at 4:27:44 PM, in mid:ab8b81216d496cec1af6fe8144c99...@biglumber.com, Greg Sabino Mullane wrote: That's exactly what the --not-dash-escaped option is for. Granted, it's not portable to some other PGP implemetations, but if there is any mailing list in world in which it would be acceptable, I would think it would be this one! :) I'm guessing that's what you did, and the cut mark was not munged. Trying the same right back at ya. Are you sure this is what the option is for? The man page says it is to enable cleartext signatures to be used with patch files. -- Best regards MFPAmailto:expires2...@rocketmail.com When it comes to humility, I'm the greatest. -BEGIN PGP SIGNATURE- iQCVAwUBTyhgAqipC46tDG5pAQpg9AP9HYu/PsjgNo2oPoQ0d+bvj0gFCSfptqNT qgnhF70S6RJltww/RPPmylKFPSQBCRgFz3RFMnBkNKWUjjYwpfN6WwvCmYjtixIE JSALrRUmOnsK9hQPJJEipjNMM9a9s5zmiIuJlv1QAX4eqIfVqvwGYiDUPjYjO8tb bm5ih9IOivc= =37wl -END PGP SIGNATURE- ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Using the not-dash-escaped option
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi On Tuesday 31 January 2012 at 10:29:53 PM, in mid:caeh5t2p4u+3nt7nlgwfjr6qh_72wlj7ygw5gabw1a1zjpss...@mail.gmail.com, Paul Hartman wrote: It's still missing the trailing space, assuming you put one there in the first place... many people don't realize it's supposed to be there. It's in my message templates with the space. Almost every line of my messages ends in a space. These are removed when I sign the message, as per the openPGP standard. I guess not-dash-escaped doesn't extend to keeping the space on the cut mark... - -- Best regards MFPAmailto:expires2...@rocketmail.com I'll tell you what's the matter! This parrot is dead! -BEGIN PGP SIGNATURE- iQCVAwUBTyiA1KipC46tDG5pAQpP1QQAm6Ac6ZNDc9GyvtHZg1Wxs3ZUQFlYkkj5 YyJ8/8uy7ECwTUIW1zFac3r6pdU1hXN57AjoWrmdCSw4uw1wiEMTcwMLNoeQLNLG Sbp5r+2So51QfGWZI/AUT609zfMaxaWmaTYQhicbeFZYXlvxlXnhBASqb7GjqQ0d uSIJtR2WCbo= =iVNn -END PGP SIGNATURE- ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Using the not-dash-escaped option
On Tue, Jan 31, 2012 at 09:41:16PM +, MFPA wrote in 516876184.20120131214116@my_localhost: That's exactly what the --not-dash-escaped option is for. Granted, it's not portable to some other PGP implemetations, but if there is any mailing list in world in which it would be acceptable, I would think it would be this one! :) I'm guessing that's what you did, and the cut mark was not munged. Trying the same right back at ya. Are you sure this is what the option is for? The man page says it is to enable cleartext signatures to be used with patch files. And for what it's worth... my client tells me the signature on this particular post you made is invalid. Your other posts to this list all pass the test ;-) Kind regards, Remco signature.asc Description: Digital signature ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
