Re: Feature request: "Security" feature

[Michael Welsh Duggan <md5i@cs.cmu.edu>]

ShengHuo ZHU <zsh@cs.rochester.edu> writes:

> Raja R Harinath <harinath@cs.umn.edu> writes:
> 
> > Hi,
> > 
> > It would be nice if the buttons, introduced in the article buffer by
> > the "gnus-*-verify-*" functions, had some useful action -- like
> > showing the output of the underlying program.
> > 
> > Say, you have the button
> > 
> >   [[PGP Verified: OK]]
> > 
> > Clicking on it would produce:
> > 
> >   [[PGP Verified: OK]
> >   Good Signature from: John Q. Signer <jqs@foo.com>
> >   No trust path established.
> >   ]
> > 
> > If we don't pay attention to the status bar while it's verifying, we
> > lose this information (looking at *Messages* is more painful than
> > clicking a button in the article).
> 
> The problem is how to capture those messages from mailcrypt or gpg.el.
> Anyone knows?

I don't know about mailcrypt, but capturing the information from
gpg.el looks quite easy.  In `mml2015-gpg-verify', the `gnus-details'
handle gets set to this information, but only if the signing failed!
If you move the clause:
            (mm-set-handle-multipart-parameter 
             mm-security-handle 'gnus-details 
             (with-current-buffer mml2015-result-buffer
               (buffer-string)))
out of the unless, you should get what you want for free.

-- 
Michael Duggan
(md5i@cs.cmu.edu)