Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <simon@josefsson.org>
Subject: Re: Sample multi-signature email [jeff covey <jeff.covey@pobox.com>] keymaps missing from console-common
Date: 24 May 2001 20:13:49 +0200	[thread overview]
Message-ID: <iluitiqy5r6.fsf@barbar.josefsson.org> (raw)
In-Reply-To: <87lmnmk6ev.fsf@cachemir.echo-net.net> (Roland Mas's message of "24 May 2001 19:23:20 +0200")

Roland Mas <mas@echo.fr> writes:

>> Here comes one mail I got from a mailing-list.  It contains a
>> forwarded message, which in turn contains another one.  All three
>> are signed.  I see three buttons, but none of them show any details
>> when clicked.
> 
> And I just saw that forwarding emails seems to break the signatures in
> them.  Dunno why.

Signatures are calculated on MIME headers as well the content -- this
makes it difficult to use a signed MIME blob out of context while
preserving the validity of the signature.  I think this was bad
design, but it's too late to fix now.

But wait, you wanted details when the signature was good?  Ah, my
previous patch only fixed details upon failures.  Try the following,
it should provide details both on success and failures.

--- mml2015.el.~6.30.~	Sat Mar 24 11:58:22 2001
+++ mml2015.el	Thu May 24 20:07:07 2001
@@ -175,8 +175,23 @@
 	      (replace-match "-----BEGIN PGP SIGNATURE-----" t t))
 	  (if (re-search-forward "^-----END PGP [^-]+-----\r?$" nil t)
 	      (replace-match "-----END PGP SIGNATURE-----" t t)))
+	(let ((mc-gpg-debug-buffer (get-buffer-create " *gnus gpg debug*")))
 	(unless (condition-case err
+		      (prog1
 		    (funcall mml2015-verify-function)
+			(if (get-buffer " *mailcrypt stderr temp")
+			    (mm-set-handle-multipart-parameter
+			     mm-security-handle 'gnus-details
+			     (with-current-buffer " *mailcrypt stderr temp"
+			       (buffer-string))))
+			(if (get-buffer " *mailcrypt stdout temp")
+			    (kill-buffer " *mailcrypt stdout temp"))
+			(if (get-buffer " *mailcrypt stderr temp")
+			    (kill-buffer " *mailcrypt stderr temp"))
+			(if (get-buffer " *mailcrypt status temp")
+			    (kill-buffer " *mailcrypt status temp"))
+			(if (get-buffer mc-gpg-debug-buffer)
+			    (kill-buffer mc-gpg-debug-buffer)))
 		  (error
 		   (mm-set-handle-multipart-parameter
 		    mm-security-handle 'gnus-details (cadr err))
@@ -187,7 +202,7 @@
 		   nil))
 	  (mm-set-handle-multipart-parameter
 	   mm-security-handle 'gnus-info "Failed")
-	  (throw 'error handle)))
+	    (throw 'error handle))))
       (mm-set-handle-multipart-parameter
        mm-security-handle 'gnus-info "OK")
       handle)))



  reply	other threads:[~2001-05-24 18:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-24 15:22 GPG signature verification Roland Mas
2001-05-24 16:10 ` Simon Josefsson
2001-05-24 17:02   ` Roland Mas
2001-05-25 10:27     ` Ulf Rompe
2001-05-24 17:06 ` Sample multi-signature email [jeff covey <jeff.covey@pobox.com>] keymaps missing from console-common Roland Mas
2001-05-24 17:23   ` Roland Mas
2001-05-24 18:13     ` Simon Josefsson [this message]
2001-05-24 17:55   ` Simon Josefsson

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=iluitiqy5r6.fsf@barbar.josefsson.org \
    --to=simon@josefsson.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).