From: "Daiki Ueno" <ueno@unixuser.org>
To: "Michaël Cadilhac" <michael@cadilhac.name>
Cc: ding@gnus.org
Subject: Re: NotDashEscaped, what?
Date: Mon, 27 Aug 2007 22:17:13 +0900 [thread overview]
Message-ID: <54a15d860708270617n7c9f5aa5w41f4404f6710dac8@mail.gmail.com> (raw)
In-Reply-To: <87fy25ci7q.fsf@cadilhac.name>
Hi,
2007/8/27, Michaël Cadilhac <michael@cadilhac.name>:
> "Daiki Ueno" <ueno@unixuser.org> writes:
> Hi! Is it on purpose that you removed the ding ML?
No, I just sent it via gmail which I'm not familiar with.
> > 2007/8/27, Michaël Cadilhac <michael@cadilhac.name>:
> >> I see more and more « NotDashEscaped: You need GnuPG to verify this
> >> message » in the shown text of mails. I think it may be a little bug.
> >>
> >> The messages read as follow:
> >>
> >> =2D----BEGIN PGP SIGNED MESSAGE-----
> >> Hash: SHA1
> >> NotDashEscaped: You need GnuPG to verify this message
> >>
> > [...]
> >> =2D----END PGP SIGNATURE-----
> >>
> >>
> >> Maybe we should discard in Gnus such a sub-header, I think what's here
> >> <http://sunsite.icm.edu.pl/gnupg/rfc2440-7.html> means that it could be
> >> discarded safely.
> >>
> >> Any strong or weak opinion?
> >
> > IMO, decoding dash-escaped text is a task of GnuPG (libraries), not of Gnus.
>
> Well, I really don't know what I'm talking about, but the point is that
> I don't want to see this NotDashEscaped. It's quite disturbing. So,
> maybe GnuPG is the culprit...
Normally GnuPG does not insert a NotDashEscaped header. I guess that
the sender (Steve Youngs) has a line "not-dash-escaped" in his
~/.gnupg/gpg.conf.
> However, I wasn't talking about decoding dash-escaped text, but more
> remove a sub-header (NotDashEscaped) together with its contents.
Yes, I know that. However, if NotDashEscaped is removed, we should
also treat the original text as *not* dash-escaped. Otherwise, the
contents you will see is not what signed in the clearsigned message.
I personally think this is not a big problem though.
> > For example, the following code returns the original text which is
> > properly decoded by GnuPG, regardless of the "clearsigned message" is
> > dash-escaped or not.
> >
> > (epg-verify-signature (epg-make-context) "clearsigned message")
>
> I don't understand what point you want to make, sorry.
I was saying that it is straightforward to make use of GnuPG's output
rather than to decode/reformat dash-escaped text by Gnus itself.
Regards,
--
Daiki Ueno
next prev parent reply other threads:[~2007-08-27 13:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-27 10:01 Michaël Cadilhac
[not found] ` <54a15d860708270349x29f0fb36g981f322a544db777@mail.gmail.com>
[not found] ` <87fy25ci7q.fsf@cadilhac.name>
2007-08-27 13:17 ` Daiki Ueno [this message]
2007-08-27 13:57 ` Michaël Cadilhac
2007-08-27 14:22 ` Daiki Ueno
2007-08-27 14:39 ` Michaël Cadilhac
2007-08-31 6:02 ` Daiki Ueno
2007-08-31 6:34 ` Leo
2007-08-31 7:43 ` Michaël Cadilhac
2007-08-31 8:38 ` 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=54a15d860708270617n7c9f5aa5w41f4404f6710dac8@mail.gmail.com \
--to=ueno@unixuser.org \
--cc=ding@gnus.org \
--cc=michael@cadilhac.name \
/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).