Gnus development mailing list
 help / color / mirror / Atom feed
From: "David Kågedal" <davidk@lysator.liu.se>
Subject: Re: pgg doesn't mention that the signature is untrusted
Date: Thu, 10 Oct 2002 18:31:18 +0200	[thread overview]
Message-ID: <u5tptuiw90p.fsf@deckard.uppsala.vtech> (raw)
In-Reply-To: <ilulm565o30.fsf@latte.josefsson.org> (Simon Josefsson's message of "Thu, 10 Oct 2002 17:08:03 +0200")

Simon Josefsson <jas@extundo.com> writes:

> David Kågedal <davidk@lysator.liu.se> writes:
>
>> PGG can tell verify signatures, and if I button2-click an extra time
>> on the button, it will give me full information about the key that
>> signed the message.  So far, so good.
>>
>> But in the pre-pgg days, when the message was signed by I can to which
>> gpg couldn't find a trust path, it would display "Utrusted: Some Name
>> <foo@bar>".  Today, you won't see that mentioned unless you click the
>> button to get full information.
>
> This is probably also because the status parsing change.  Does loading
> contrib/gpg.el help?  If someone would like to remove the use of
> `gpg-unabbrev-trust-alist' in mml2015.el it would help.

I loaded contrib/gpg.el in my running gnus, and it made no difference.

-- 
David Kågedal



  parent reply	other threads:[~2002-10-10 16:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-10 12:50 David Kågedal
2002-10-10 15:08 ` Simon Josefsson
2002-10-10 15:23   ` Josh Huber
2002-10-10 15:47     ` Simon Josefsson
2002-10-10 16:31   ` David Kågedal [this message]
2002-10-10 16:41     ` Simon Josefsson
2002-10-10 17:14       ` David Kågedal
2002-10-10 18:44       ` Mark Trettin
2002-10-10 20:21         ` Simon Josefsson
2002-10-11  0:39           ` Josh Huber
2002-10-11  1:08             ` Simon Josefsson
2002-10-11  1:30               ` Josh Huber
2002-10-11  4:17                 ` Simon Josefsson
2002-10-17 10:57                   ` Mark Trettin

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=u5tptuiw90p.fsf@deckard.uppsala.vtech \
    --to=davidk@lysator.liu.se \
    /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).