From: "Mark D. Baushke" <mdb@gnu.org>
Cc: mh-e-devel@lists.sourceforge.net
Subject: Gnus 5.10.6 problems with PGP/MIME (test cases)
Date: Wed, 11 Jan 2006 17:12:34 -0800 [thread overview]
Message-ID: <19643.1137028354@juniper.net> (raw)
Background:
This problem arises using MH-E 7.85+cvs plus Gnus v5.10.6
running under GNU Emacs 21.4 on a Gentoo GNU/Linux box.
Problem (first message in attachment):
Content-Type: text/plain; charset="us-ascii"; format=flowed
does not properly allow the GNUS 5.10.6 mml-* functions to recognize
that there is a PGP Signed message body. If the format=flowed clause is
removed, then there is no problems with this recognition. I get this ';
format=flowed' addition to the Content-Type even for PGP messages that
are encrypted by Eudora users all the time.
Problem (third message in attachment):
Content-Type: application/pgp; x-action=sign; format=text
does not properly allow GNUS 5.10.6 mml-* function to display
the text or signature information. Note that I do understand that
this Content-Type is mentioned in RFC 2015 as being a bad idea.
However, I get this kind of Content-Type from some mutt users and
a few other Windows users.
The second message in the attachment decodes properly and will say
[[PGP Signed Part:Undecided]] until the user requests that the
signature be verified in which case it displays
[[PGP Signed Part:Mark D Baushke <mdb@gnu.org>]]
in the short form or
[[PGP Signed Part:Mark D Baushke <mdb@gnu.org>]
Signature made Wed Jan 11 16:44:25 2006 PST using DSA key ID 6B039C51
Good signature from "Mark D Baushke <mdb@gnu.org>"
[GNUPG:] SIG_ID 5DWnGnqCMbs+B1YcmM1o/2+BDiw 2006-01-12 1137026665
[GNUPG:] GOODSIG 0A0EC03C6B039C51 Mark D Baushke <mdb@gnu.org>
[GNUPG:] VALIDSIG A83FF00BF7002712D36A9F3A0A0EC03C6B039C51 2006-01-12 1137026665 0 3 0 17 2 01 A83FF00BF7002712D36A9F3A0A0EC03C6B039C51
[GNUPG:] TRUST_FULLY
]
in the long form.
A similar set of problems arise when the PGP/MIME message is encrypted.
For the application/pgp form the encrypted Content-Type generated by
mutt looks like this:
Content-Type: application/pgp; x-action=encrypt; format=text
Please let me know if you have any questions.
Thanks,
-- Mark
The shell archive below contains an mbox-style formatted file with two
messages. The messages are identical except that one
#!/bin/sh
# This is a shell archive (produced by GNU sharutils 4.2.1).
# To extract the files from this archive, save it to some FILE, remove
# everything before the `!/bin/sh' line above, then type `sh FILE'.
#
# Made on 2006-01-11 16:58 PST by <mdb@gnu.org>.
# Source directory was `/home/m/mdb'.
#
# Existing files will *not* be overwritten unless `-c' is specified.
#
# This shar contains:
# length mode name
# ------ ---------- ------------------------------------------
# 1606 -rw-r--r-- /homes/mdb/gnus.msg
#
save_IFS="${IFS}"
IFS="${IFS}:"
gettext_dir=FAILED
locale_dir=FAILED
first_param="$1"
for dir in $PATH
do
if test "$gettext_dir" = FAILED && test -f $dir/gettext \
&& ($dir/gettext --version >/dev/null 2>&1)
then
set `$dir/gettext --version 2>&1`
if test "$3" = GNU
then
gettext_dir=$dir
fi
fi
if test "$locale_dir" = FAILED && test -f $dir/shar \
&& ($dir/shar --print-text-domain-dir >/dev/null 2>&1)
then
locale_dir=`$dir/shar --print-text-domain-dir`
fi
done
IFS="$save_IFS"
if test "$locale_dir" = FAILED || test "$gettext_dir" = FAILED
then
echo=echo
else
TEXTDOMAINDIR=$locale_dir
export TEXTDOMAINDIR
TEXTDOMAIN=sharutils
export TEXTDOMAIN
echo="$gettext_dir/gettext -s"
fi
if touch -am -t 200112312359.59 $$.touch >/dev/null 2>&1 && test ! -f 200112312359.59 -a -f $$.touch; then
shar_touch='touch -am -t $1$2$3$4$5$6.$7 "$8"'
elif touch -am 123123592001.59 $$.touch >/dev/null 2>&1 && test ! -f 123123592001.59 -a ! -f 123123592001.5 -a -f $$.touch; then
shar_touch='touch -am $3$4$5$6$1$2.$7 "$8"'
elif touch -am 1231235901 $$.touch >/dev/null 2>&1 && test ! -f 1231235901 -a -f $$.touch; then
shar_touch='touch -am $3$4$5$6$2 "$8"'
else
shar_touch=:
echo
$echo 'WARNING: not restoring timestamps. Consider getting and'
$echo "installing GNU \`touch', distributed in GNU File Utilities..."
echo
fi
rm -f 200112312359.59 123123592001.59 123123592001.5 1231235901 $$.touch
#
if mkdir _sh14108; then
$echo 'x -' 'creating lock directory'
else
$echo 'failed to create lock directory'
exit 1
fi
# ============= /homes/mdb/gnus.msg ==============
if test ! -d '/homes'; then
$echo 'x -' 'creating directory' '/homes'
mkdir '/homes'
fi
if test ! -d '/homes/mdb'; then
$echo 'x -' 'creating directory' '/homes/mdb'
mkdir '/homes/mdb'
fi
if test -f '/homes/mdb/gnus.msg' && test "$first_param" != -c; then
$echo 'x -' SKIPPING '/homes/mdb/gnus.msg' '(file already exists)'
else
$echo 'x -' extracting '/homes/mdb/gnus.msg' '(text)'
sed 's/^X//' << 'SHAR_EOF' > '/homes/mdb/gnus.msg' &&
XFrom mdb@gnu.org Wed Jan 11 16:45:06 2006
To: mdb@gnu.org
XFrom: "Mark D. Baushke" <mdb@gnu.org>
Subject: test pgp message
Content-Type: text/plain; charset="us-ascii"; format=flowed
Mime-Version: 1.0
Date: Wed, 11 Jan 2006 16:45:06 -0800
Message-ID: <13570.1137026706@fencepost.gnu.org>
X
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
X
This is a test.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
X
iD8DBQFDxaZpCg7APGsDnFERAgolAJ9+VbmaXTgWiMTEl4Y2gSQOGF3zHQCfR7MZ
tns6uRALb5LuMSIQMdbm6E4=
=SycC
-----END PGP SIGNATURE-----
X
XFrom mdb@gnu.org Wed Jan 11 16:45:06 2006
To: mdb@gnu.org
XFrom: "Mark D. Baushke" <mdb@gnu.org>
Subject: test pgp message
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0
Date: Wed, 11 Jan 2006 16:45:06 -0800
Message-ID: <13570.1137026706@fencepost.gnu.org>
X
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
X
This is a test.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
X
iD8DBQFDxaZpCg7APGsDnFERAgolAJ9+VbmaXTgWiMTEl4Y2gSQOGF3zHQCfR7MZ
tns6uRALb5LuMSIQMdbm6E4=
=SycC
-----END PGP SIGNATURE-----
X
XFrom mdb@gnu.org Wed Jan 11 16:45:06 2006
To: mdb@gnu.org
XFrom: "Mark D. Baushke" <mdb@gnu.org>
Subject: test pgp message
Content-Type: application/pgp; x-action=sign; format=text
Mime-Version: 1.0
Date: Wed, 11 Jan 2006 16:45:06 -0800
Message-ID: <13570.1137026706@fencepost.gnu.org>
X
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
X
This is a test.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
X
iD8DBQFDxaZpCg7APGsDnFERAgolAJ9+VbmaXTgWiMTEl4Y2gSQOGF3zHQCfR7MZ
tns6uRALb5LuMSIQMdbm6E4=
=SycC
-----END PGP SIGNATURE-----
X
SHAR_EOF
(set 20 06 01 11 16 57 41 '/homes/mdb/gnus.msg'; eval "$shar_touch") &&
chmod 0644 '/homes/mdb/gnus.msg' ||
$echo 'restore of' '/homes/mdb/gnus.msg' 'failed'
if ( md5sum --help 2>&1 | grep 'sage: md5sum \[' ) >/dev/null 2>&1 \
&& ( md5sum --version 2>&1 | grep -v 'textutils 1.12' ) >/dev/null; then
md5sum -c << SHAR_EOF >/dev/null 2>&1 \
|| $echo '/homes/mdb/gnus.msg:' 'MD5 check failed'
7c902d121e94e6df39e643e77ba4fb1c /homes/mdb/gnus.msg
SHAR_EOF
else
shar_count="`LC_ALL= LC_CTYPE= LANG= wc -c < '/homes/mdb/gnus.msg'`"
test 1606 -eq "$shar_count" ||
$echo '/homes/mdb/gnus.msg:' 'original size' '1606,' 'current size' "$shar_count!"
fi
fi
rm -fr _sh14108
exit 0
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
next reply other threads:[~2006-01-12 1:12 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-12 1:12 Mark D. Baushke [this message]
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
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=19643.1137028354@juniper.net \
--to=mdb@gnu.org \
--cc=mh-e-devel@lists.sourceforge.net \
/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).