Hi Krysztof, Do you know about bazaar's revision signing mechanism? See this blog post for instructions: <a href="http://blogs.gnome.org/jamesh/2007/10/04/signed-revisions-with-bazaar/">http://blogs.gnome.org/jamesh/2007/10/04/signed-revisions-with-bazaar/</a> I believe this would fit your requirements somewhat... though potentially won't address all of them. Cheers, Philip <div class="gmail_quote">On Tue, Mar 8, 2011 at 3:34 AM, Krzysztof Nowicki <<a href="mailto:krissn@op.pl">krissn@op.pl</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Hi, I'm trying to setup an internal portal hosting shared Bazaar repositories. The idea is to give anyone write access to the repositories as I don't want restrict user commit rights to the branches. What I however want is to be able to identify who committed every revision so that in case someone abuses the trust and pushes some bogus revision. The problem that I found is that when a push occurs to the repository, all revisions are stored without changes. This means that whatever committer name was given will also appear in the public repository. What will however not be there is the real name of whoever pushed that change. What I'm looking for is a way to log the real committer name (who is authenticated upon access to the server using an individual SSH key) along with the pushed revisions so that if something bad happens I can beyond any doubt identify the offender. Is there a way to do this with Bazaar? Krzysztof </blockquote></div> -- Philip Peitsch Mob: 0439 810 260