From: "Daiki Ueno" <ueno@unixuser.org>
To: "Reiner Steib" <Reiner.Steib@gmx.de>, ding@gnus.org
Subject: Re: PGG: "NotDashEscaped: You need GnuPG to verify this message"
Date: Tue, 8 Jan 2008 18:42:07 +0900 [thread overview]
Message-ID: <54a15d860801080142l70b95d7dkac4bf51a86196011@mail.gmail.com> (raw)
In-Reply-To: <v9zlvhe1ks.fsf@marauder.physik.uni-ulm.de>
2008/1/8, Reiner Steib <reinersteib+gmane@imap.cc>:
> > I think that my ChangeLog entry is not clear.
>
> Could you please install the improved text?
I thought again, and concluded that the one I previously posted is too
descriptive.
> Is this (very naive) patch correct?
>
> + (when (looking-at "NotDashEscaped: You need GnuPG to verify this message$")
> + (forward-line))
Not exactly. You should disable unescaping dashes in this case.
Please read http://thread.gmane.org/gmane.emacs.gnus.general/65087/focus=65109
> I'm not familiar with the mml2015.el code at all. After some my very
> limited code read and test, I conclude that
> `mml2015-extract-cleartext-signature' is only used to massage the
> displayed text of the article buffer. Verification
> (e.g. `mml2015-pgg-clear-verify') is done using the original
> ("un-massaged" text). Is that correct?
Yes, but if the displayed text is different from the verified text,
what the purpose of digital signatures.
> Could you please add a doc string to this function?
I still believe that the right way is to use the plaintext output from
GnuPG as it is, and
mml2015-extract-cleartext-signature is just a kludge for misdesigned
libraries like PGG, which have no ability to do that. So, I think it
should not have descriptive documentation.
Regards,
--
Daiki Ueno
prev parent reply other threads:[~2008-01-08 9:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-06 9:58 Reiner Steib
2008-01-06 12:23 ` Daiki Ueno
2008-01-06 14:10 ` Reiner Steib
2008-01-07 3:22 ` Daiki Ueno
2008-01-07 22:02 ` Reiner Steib
2008-01-08 9:42 ` Daiki Ueno [this message]
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=54a15d860801080142l70b95d7dkac4bf51a86196011@mail.gmail.com \
--to=ueno@unixuser.org \
--cc=Reiner.Steib@gmx.de \
--cc=ding@gnus.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).