From: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: mdb@gnu.org, mh-e-devel@lists.sourceforge.net, ding@gnus.org
Subject: Re: Gnus 5.10.6 problems with PGP/MIME (test cases)
Date: Tue, 07 Feb 2006 16:46:25 +0900 [thread overview]
Message-ID: <b4mek2fa9wu.fsf@jpl.org> (raw)
In-Reply-To: <b258afad-11cd-4abc-99ba-89c99615ef53@well-done.deisui.org>
>>>>> In <b258afad-11cd-4abc-99ba-89c99615ef53@well-done.deisui.org>
>>>>> Daiki Ueno wrote:
>>>>>> In <b4mpsmp3e11.fsf@jpl.org>
>>>>>> Katsumi Yamaoka <yamaoka@jpl.org> wrote:
>> Thank you for the information. I roughly understood that
>> `gpg --textmode' generates a *text* packet and recipients should
>> treat it as text because it is *text*.
> Though I have not yet read entire discussion, you are talking about
> non-MIME encryption?
No, I thought that it includes not only non-MIME encryption but
also MIME encryption.
> If so, it might be preferable that --textmode is specified only in
> that case. If --textmode is specified, gpg _itself_ converts line
> ending.
`pgg-gpg-encrypt-region' always inserts CR in every line ending
of text using `(pgg-as-lbt START END 'CRLF BODY)'. So, if the
--textmode option is not specified, gpg doesn't treat sending
data as text and recipients will see ^Ms in a decrypted message.
However, only recipients who use Gnus will never see ^Ms because
`pgg-gpg-process-region' uses `raw-text-dos' when reading a
decrypted message from a temp file, and furthermore,
`mml2015-pgg-decrypt' converts CRLF to LF.
> On the GNU/Linux system:
> $ ruby -e 'puts("abc\r\ndef\r\nghi\r\n")' > test.txt
> $ gpg -q --encrypt --textmode -r ueno@unixuser.org test.txt
> $ gpg -q --decrypt test.txt.gpg > test.txt
> You need a passphrase to unlock the secret key for
> user: "Daiki Ueno <ueno@unixuser.org>"
> ...
> $ hd test.txt
> 00000000 61 62 63 0a 64 65 66 0a 67 68 69 0a |abc.def.ghi.|
> 0000000c
> All CRLF are converted to LF.
Yes, that's right.
> This might cause a problem if you send an
> encrypted and signed data in RFC1847 encapsulation (RFC3156, section
> 6.1). After decryption, it does no longer contain the signed material
> identical as before encryption.
That's indeed a problem. Do you know the way to verify it using
Gnus? I don't know what mml command do that. In addition, do
you have an idea to solve the ^Ms problem that I mentioned above?
> Please add *me* to the Cc: list if you mention changes obviously
> conflicting with my intension such as below. Otherwise, I will not be
> aware of them.
I'm sorry to have not informed it to you. I must do it from the
next time. I thought informing it to you was not necessary
because I found out someone added --textmode in Gnus of the
Emacs version (i.e., Gnus v5.11) before I did it. I couldn't
discover who did it in Emacs when, though.
next prev parent reply other threads:[~2006-02-07 7:46 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 [this message]
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=b4mek2fa9wu.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=ding@gnus.org \
--cc=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).