monotone-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Monotone-devel] [RFC] versioned policy -- introduction


From: Daniel Carosone
Subject: Re: [Monotone-devel] [RFC] versioned policy -- introduction
Date: Thu, 7 Sep 2006 17:15:35 +1000
User-agent: Mutt/1.5.13 (2006-08-11)

On Thu, Sep 07, 2006 at 09:07:43AM +0200, Richard Levitte - VMS Whacker wrote:
> In message <address@hidden> on Thu, 07 Sep 2006 09:06:15 +0200 (CEST), 
> Richard Levitte - VMS Whacker <address@hidden> said:
> 
> richard> I still don't understand why keys would be stored by name.  In the
> richard> rest of the security community, keys are identified by a form of 
> hash,
> richard> or a fingerprint if you will.  There is of course the usual risk that
> richard> you can get two keys with the same hash (fingerprint), but since a 
> key
> richard> has certain properties and a structure that can't be altered without
> richard> invalidating it, the risk is minimal, so in essense, you can
> richard> practically say that there's a 1:1 mapping between keys and their
> richard> fingerprint.
> 
> Oh, and I'm not saying that *users* should have to identify keys by
> key id, just the software itself.


Yeah. I expect one of the policy statments that go in these branches
is roughly of the meaning:

  id X gets to use the name Y

This might/will/should apply to several kinds of things: keys,
branches, namespaces/aliases (like "nvm."), etc.

--
Dan.

Attachment: pgpW93ClUvSCh.pgp
Description: PGP signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]