Gnus development mailing list
 help / color / mirror / Atom feed
From: Andreas Fuchs <asf@acm.org>
Subject: Re: gnus-insert-mime-security-button
Date: Fri, 29 Dec 2000 19:13:29 +0100	[thread overview]
Message-ID: <E14C41x-0000OF-00@dahaIM.dyndns.org> (raw)
In-Reply-To: <vafg0j7mfmm.fsf@lucy.cs.uni-dortmund.de>

[-- Attachment #1: Type: text/plain, Size: 903 bytes --]

Today, Kai Großjohann <Kai.Grossjohann@CS.Uni-Dortmund.DE> wrote:
> So maybe Gnus should suppress the signed parts where the verification
> failed and print

>         FORGED CONTENT SNIPPED
> in large friendly letters, instead.

Eeeek. That would make it a little difficult to read mailing lists where
people sign their mails by default (debian-devel, for example) while
their keys are not in your keyring.

Having faces for the different possibilities (check failed, check OK but
key untrusted, check OK and key trusted) would be nice, I think (a
multi-coloured sidebar, anyone?).

Assuming that signed content for which the check fails is forged by
default would be too confusing and annoying, IMHO -- think bad MTAs and
MUAs which don't do PGP content right.

(Proof by example: is this message forged? (-:)

-- 
Andreas Fuchs, <asf@acm.org>, <d96001@htlwrn.ac.at>, antifuchs

[-- Attachment #2: Type: application/pgp-signature, Size: 231 bytes --]

  reply	other threads:[~2000-12-29 18:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-29 12:54 gnus-insert-mime-security-button Lars Magne Ingebrigtsen
2000-12-29 13:56 ` gnus-insert-mime-security-button Kai Großjohann
2000-12-29 14:16   ` gnus-insert-mime-security-button Lars Magne Ingebrigtsen
2000-12-29 15:06     ` gnus-insert-mime-security-button Kai Großjohann
2000-12-29 18:13       ` Andreas Fuchs [this message]
2000-12-29 18:46         ` gnus-insert-mime-security-button Graham Murray
2000-12-29 18:58           ` gnus-insert-mime-security-button Andreas Fuchs

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=E14C41x-0000OF-00@dahaIM.dyndns.org \
    --to=asf@acm.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).