unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: 74630@debbugs.gnu.org
Subject: bug#74630: 31.0.50; emacs-mail-verify
Date: Sun, 01 Dec 2024 14:53:46 +0200	[thread overview]
Message-ID: <868qsz5ztx.fsf@gnu.org> (raw)
In-Reply-To: <E1tHcfc-0004mm-UT@fencepost.gnu.org> (message from Richard Stallman on Sun, 01 Dec 2024 00:39:00 -0500)

> From: Richard Stallman <rms@gnu.org>
> Date: Sun, 01 Dec 2024 00:39:00 -0500
> 
> 
> The doc string of `emacs-mail-verify' does not say how it
> indicates that the signature is valid, or how it indicates
> that the signature is not valid.

I guess you meant epa-mail-verify?

> Would someone please add that to its doc string?

Not sure what you expected the doc string to say.  Would the below be
enough?

  Verify OpenPGP cleartext signed messages in the current buffer.
  The buffer is expected to contain a mail message.

  If the verification fails, the command signals an error.

The last sentence describes the following snippet from
epa-verify-region, which epa-mail-verify calls:

    (unless (epg-context-result-for context 'verify)
      (error "Unable to verify region"))

There are also other reasons to signal an error, e.g. if there are no
"-----BEGIN PGP SIGNED MESSAGE-----" line.  But eventually, all of the
problems cause an error.

If this is somehow not detailed enough, then I'm afraid someone else,
who knows the code, will have to improve the doc string, because I
could see no clear description in the code what values could the
context-result have and what is the meaning of each result.  Maybe I
missed something.





  reply	other threads:[~2024-12-01 12:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-01  5:39 bug#74630: 31.0.50; emacs-mail-verify Richard Stallman
2024-12-01 12:53 ` Eli Zaretskii [this message]
2024-12-04  6:09   ` Richard Stallman
2024-12-04 13:26     ` Eli Zaretskii

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=868qsz5ztx.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=74630@debbugs.gnu.org \
    --cc=rms@gnu.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).