Enforcing usernames
Lasse Kliemann
lasse-list-mercurial-2009 at mail.plastictree.net
Fri Jun 12 01:07:41 CDT 2009
* Message by -Thomas Burdick- from Wed 2009-06-03:
> It looks like some work has been done on this extension, I was wondering
> what still needed to be done as I actually need this!
>
> Its important in certain legal situations where the owner of changes must be
> verifiable. Really. Cryptographic signatures solve this problem in a really
> nice way but it must be enforced on commit/push/pull.
>
> So really, I'm more than willing to help make this little extension work,
> and work really well. It'd be great if it were included with mercurial at
> some point as well.
Which extension do you mean? Commitsigs or my collection at
http://plastictree.homeunix.net:8080/hg.cgi/hgssh ?
The latter is finished and documented. I use it for production.
It does not use (need) crypto, just enforces usernames and puts
all trust in a central server, like one would have with Subversion.
Suggestions are welcome.
Working on Commitsigs is still on my TODO list.
-------------- 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/20090612/a631965d/attachment.pgp
More information about the Mercurial
mailing list