[ANN] autosign extension
Lasse Kliemann
lasse-list-mercurial-2009 at mail.plastictree.net
Sat May 16 08:43:02 CDT 2009
* Message by -Lasse Kliemann- from Fri 2009-05-15:
> On the long run, I would clearly vote for extending the 'log'
> functionality to show with each changeset how things are
> concerning the signature. Maybe nothing should be shown for case
> 1., and some easy-to-recognize warning should be shown in one of
> the other cases. Since verifying signatures takes time, we would
> have to think about caching.
I picture an output of 'hg log' like this one:
1. user [not verified]: John Doe <john.doe at example.com>
2. user [INVALID]: John Doe <john.doe at example.com>
3. user: John Doe <john.doe at example.com>
So, there are three alternatives. The first one means that there
was no signature for the changeset.
The second means that there was a signature, but it either is a
bad signature, no matching public key was found, or there is no
public key with a trusted user ID that matches the displayed
username.
The third one is displayed for all other cases, and if I haven't
overlooked something, this means that there is a valid testimony
for authorship by someone known as "John Doe <john.doe at example.com>"
(in the context of the local trust system).
About terminology. There seems to be no generally accepted exact
use of "verify". Sometimes it's used relative to a public key,
meaning that the signature decrypts correctly with that key; no
statement about user IDs. At other times, it's used in
conjunction with user IDs. Since for our purposes, the connection
to user IDs is essential, I suggest that we use "verify" usually
in that sense. If only a signature and a public key is given, we
could speak of "good signature for that key" or "bad signature
for that key", leaning on GnuPG terminology.
Some days ago, Martin asked for a better name for command
'checksigs', and whether it might better be called 'verifysigs'.
I think that 'verifyauthors' is closest to describing what it
does (or what it will do, when it's finished). However, since the
Mercurial term for 'author' is 'user' (see 'hg log'), it might be
best to call it 'verifyusers'.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
Url : http://selenic.com/pipermail/mercurial/attachments/20090516/948bb830/attachment.pgp
More information about the Mercurial
mailing list