From: Philip Hands <phil@hands.com>
To: notmuch@notmuchmail.org
Subject: Re: Ultimate trust
Date: Sun, 22 Mar 2020 20:15:35 +0100 [thread overview]
Message-ID: <87d094ciaw.fsf@hands.com> (raw)
In-Reply-To: <87pnd4laxa.fsf@fliptop.i-did-not-set--mail-host-address--so-tickle-me>
[-- Attachment #1: Type: text/plain, Size: 1361 bytes --]
Tomas Nordin <tomasn@posteo.net> writes:
> Teemu Likonen <tlikonen@iki.fi> writes:
...
>> I do this: I press "Yes" (to trust "ultimately") but then immediately go
>> edit ~/.gnupg/trustlist.txt file and put "!" mark in the beginning of
>> that certificate authority's key fingerprint. It marks that key
>> untrusted (because I really don't know). Then: "gpgconf --reload
>> gpg-agent".
>
> OK, thanks. That already feels better, knowing I can revert this trust
> easily like that. And some better understanding for whats going on.
That seems like a UI bug to me -- I'd have thought that there should be
a "No" button so that you can stop it repeatedly asking (presumably by
automatically doing the same as the above manual procedure).
Would anyone happen to know where that should be reported?
I have a feeling that I'd want to default that to answering "No", and
never see the prompt.
The number of people I'm willing to declare ultimate trust in is quite
limited, and even for those, I'm not going to do it via some unfamiliar
bit of UI that springs up unexpectedly. This strikes me as mildly
deranged, and appears to be trying to train users to do the wrong thing.
Cheers, Phil.
--
|)| Philip Hands [+44 (0)20 8530 9560] HANDS.COM Ltd.
|-| http://www.hands.com/ http://ftp.uk.debian.org/
|(| Hugo-Klemm-Strasse 34, 21075 Hamburg, GERMANY
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2020-03-22 19:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-21 14:37 Ultimate trust Tomas Nordin
2020-03-21 15:43 ` Teemu Likonen
2020-03-22 14:30 ` Tomas Nordin
2020-03-22 19:15 ` Philip Hands [this message]
2020-03-22 22:21 ` Tomas Nordin
2020-03-23 1:20 ` David Bremner
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://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d094ciaw.fsf@hands.com \
--to=phil@hands.com \
--cc=notmuch@notmuchmail.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://yhetil.org/notmuch.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).