Enforcing usernames

[Thomas Burdick]

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.

-Tom

On Wed, May 27, 2009 at 6:13 AM, Martin Geisler <mg at lazybytes.net> wrote:

> Lasse Kliemann <lasse-list-mercurial-2009 at mail.plastictree.net>
> writes:
>
> > * Message by -Martin Geisler- from Wed 2009-05-27:
> >
> >> >    xrange(repo[node], len(repo))
> >> >
> >> > I took this from the acl extension.
> >
> > Ok, so this is guaranteed to capture every changeset of the incoming
> > changegroup? This is important here, since no incoming changeset
> > shall go unchecked.
>
> Yeah, that's the idea. When the hook is used as a pretxnchangegroup,
> the 'node' parameter will be something like '8a3b2a309c8a' and this is
> the first changeset in the group just pushed. Your code converts it to
> a revision number, say 37, and iterates over 37, 38, ... tip.
>
> --
> Martin Geisler
>
> VIFF (Virtual Ideal Functionality Framework) brings easy and efficient
> SMPC (Secure Multiparty Computation) to Python. See: http://viff.dk/.
> _______________________________________________
> Mercurial mailing list
> Mercurial at selenic.com
> http://selenic.com/mailman/listinfo/mercurial
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://selenic.com/pipermail/mercurial/attachments/20090603/77c1dafe/attachment.htm