From: "Mark D. Baushke" <mdb@gnu.org>
Cc: Daiki Ueno <ueno@unixuser.org>,
ding@gnus.org, mh-e-devel@lists.sourceforge.net
Subject: Re: Gnus 5.10.6 problems with PGP/MIME (test cases)
Date: Wed, 08 Feb 2006 22:40:11 -0800 [thread overview]
Message-ID: <82735.1139467211@juniper.net> (raw)
In-Reply-To: <b4mk6c53wwn.fsf@jpl.org>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: multipart/mixed; boundary="==-=-=", Size: 3354 bytes --]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
- --==-=-=
Content-Transfer-Encoding: quoted-printable
Well, the patch didn't work cleanly in my gnus-5.10.6 tree, so
I did this:
cvs -d :pserver:gnus@cvs.gnus.org:/usr/local/cvsroot co -r v5-10 gnus
cd gnus
./configure --prefix=3D~/elisp/gnus-5.10.6+cvs
make
make install
and then added the new directory to my load-path and re-compiled my
MH-E.
It may be due to the new version, but I am now seeing that mixing
a '#secure method=3Dpgp mode=3Dsignencrypt' section along with a
'#part type=3D"text/plain "filename=3D"~msg1.txt" disposition=3Dattachment
description=3D"a copy of the message as an attachment"'
'#/part'
(all inside angle brackets where appropraite) somehow only does a
mode=3Dencrypt on the message.)
I also notice that if I have a message with a 0x0D character in it or
full \r\n line endings and I just send a encrypted text message with
method=3Dpgp, that the resulting decoded message uses \n line endings on
my FreeBSD box and all 0x0D characters have been removed.
However, if I attach a DOS format file with \r\n line endings to a
message that has \r\n line endings, that the resulting decoded message
has a '=3D0xD' on the end of all of the lines that were originally \r\n
line endings.
Thanks,
-- Mark
The really odd thing about this mesage was that I secified
| <#secure method=3Dpgp mode=3Dsignencrypt sender=3D0x6B039C51>
| abc=0D
| efg=0D
| hij=0D
| =0D
| This file has control-M characters at the end of each line.=0D
|=20
- --==-=-=
Content-Disposition: attachment; filename=msg1.txt
Content-Transfer-Encoding: quoted-printable
Content-Description: a copy of the message as an attachment
abc=0D
efg=0D
hij=0D
=0D
This file has control-M characters at the end of each line.=0D
- --==-=-=
the 'method=pgp mode=signencrypt' should have generated a signed and
encrypted message, but instead it only generated an encrypted message.
To: mdb@gnu.org
From: "Mark D. Baushke" <mdb@gnu.org>
Subject: test message
X-Mailer: MH-E 7.91+cvs; nmh 1.0.4; GNU Emacs 21.3.1
Date: Wed, 08 Feb 2006 22:33:40 -0800
[[PGP Encrypted Part:OK]]
- --=-=-=
Content-Transfer-Encoding: quoted-printable
abc=0D
efg=0D
hij=0D
=0D
This file has control-M characters at the end of each line.=0D
- --=-=-=
Content-Disposition: attachment; filename=msg1.txt
Content-Transfer-Encoding: quoted-printable
Content-Description: a copy of the message as an attachment
abc=0D
efg=0D
hij=0D
=0D
This file has control-M characters at the end of each line.=0D
- --=-=-=--
[[End of PGP Encrypted Part]]
For completeness, here is the MH-E version I am using:
M-x mh-version RET
MH-E 7.91+cvs
MH-E compilation details:
Byte compiled: yes
Gnus (compile-time): Gnus v5.10.7
Gnus (run-time): Gnus v5.10.7
GNU Emacs 21.3.1 (i386--freebsd, X toolkit, Xaw3d scroll bars)
of 2003-07-11 on rat48.juniper.net
nmh 1.0.4
mh-progs: /usr/local/bin
mh-lib: /usr/local/etc/nmh
mh-lib-progs: /usr/local/libexec/nmh
FreeBSD sapphire.juniper.net 4.10-RELEASE-p2 FreeBSD 4.10-RELEASE-p2 #0: Wed Sep 15 14:24:39 PDT 2004 root@mailspare2.juniper.net:/usr/obj/usr/src/sys/mailspare2 i386
- --==-=-=--
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)
iD8DBQFD6uPLCg7APGsDnFERAvrCAJwLYYwapxKZqBh110oYfHbmU1r65wCfQETf
hT8RO4C1zf1kC3itgVapRSg=
=mU3E
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2006-02-09 6:40 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-12 1:12 Mark D. Baushke
2006-01-13 23:24 ` Reiner Steib
2006-01-14 2:58 ` Mark D. Baushke
2006-01-14 14:58 ` Katsumi Yamaoka
2006-01-16 0:39 ` Katsumi Yamaoka
2006-01-16 6:36 ` Mark D. Baushke
2006-01-16 7:58 ` Katsumi Yamaoka
2006-01-16 8:41 ` Katsumi Yamaoka
2006-01-16 9:00 ` Katsumi Yamaoka
2006-01-16 19:17 ` Bill Wohler
2006-01-16 19:48 ` Mark D. Baushke
2006-01-17 7:35 ` Katsumi Yamaoka
2006-01-17 9:00 ` Mark D. Baushke
2006-01-17 10:53 ` Katsumi Yamaoka
2006-01-17 18:17 ` Mark D. Baushke
2006-01-18 5:33 ` Katsumi Yamaoka
2006-01-18 10:04 ` Mark D. Baushke
2006-01-18 12:40 ` Katsumi Yamaoka
2006-01-18 17:25 ` Mark D. Baushke
2006-01-18 17:29 ` Mark D. Baushke
2006-01-19 6:01 ` Katsumi Yamaoka
2006-01-19 9:13 ` Mark D. Baushke
2006-01-19 6:01 ` Synch of PGG (was Re: Gnus 5.10.6 problems with PGP/MIME (test cases)) Katsumi Yamaoka
2006-01-19 11:53 ` Synch of PGG Katsumi Yamaoka
2006-01-19 13:01 ` Simon Josefsson
2006-01-19 13:38 ` Reiner Steib
2006-01-19 13:47 ` Miles Bader
2006-01-19 14:48 ` Katsumi Yamaoka
2006-02-07 4:53 ` Gnus 5.10.6 problems with PGP/MIME (test cases) Daiki Ueno
2006-02-07 7:12 ` Mark D. Baushke
2006-02-07 7:46 ` Katsumi Yamaoka
2006-02-07 8:57 ` Daiki Ueno
2006-02-07 9:40 ` Mark D. Baushke
[not found] ` <9bda6607-510b-468c-bd1e-ec9b8865cdd2@well-done.deisui.org>
[not found] ` <15566.1139355525@juniper.net>
2006-02-08 8:09 ` Daiki Ueno
2006-02-08 8:30 ` Katsumi Yamaoka
2006-02-08 9:06 ` Daiki Ueno
2006-02-08 9:55 ` Katsumi Yamaoka
2006-02-09 5:24 ` Daiki Ueno
2006-02-09 5:29 ` Daiki Ueno
2006-02-09 5:48 ` Katsumi Yamaoka
2006-02-09 6:40 ` Mark D. Baushke [this message]
2006-02-09 6:44 ` Mark D. Baushke
2006-02-09 7:31 ` Katsumi Yamaoka
2006-02-09 7:42 ` Mark D. Baushke
[not found] ` <82857.1139467447-3r7Miqu9kMnR7s880joybQ@public.gmane.org>
2006-02-09 8:27 ` refered article lookup (was: Gnus 5.10.6 problems with PGP/MIME (test cases)) Jochen Küpper
2006-02-09 9:19 ` refered article lookup Katsumi Yamaoka
2006-02-08 15:27 ` Gnus 5.10.6 problems with PGP/MIME (test cases) Mark D. Baushke
2006-02-07 10:02 ` Katsumi Yamaoka
2006-02-07 23:40 ` Daiki Ueno
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=82735.1139467211@juniper.net \
--to=mdb@gnu.org \
--cc=ding@gnus.org \
--cc=mh-e-devel@lists.sourceforge.net \
--cc=ueno@unixuser.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).