bzr_access installation and usage

[Eugene Wee]

Hi,

On Sun, Oct 18, 2009 at 8:11 PM, Stephen J. Turnbull <stephen at xemacs.org> wrote:
> I don't see how you propose to track them *by key*, though.

What do you mean by "track them *by key*"?

Currently, I am about to use bzr_access to just control who can access
which repository. My current setup is one where I create user accounts
on the server (my own VPS) for each of my project-based university
modules, and hand out the respective passwords to my group members.
This means that a group member from module A who takes module B but
who is not my fellow group member in module B can "refer" to my module
B project work, besides being able to take a look at various other
aspects of my system. I have not cared about this for a long time,
until recently when I saw bzr_access being touted quite a few times on
the mailing list, and a group member did comment on the weakness of my
setup.

So, I am not too concerned about a group member impersonating another
to do something stupid, because if we find out that person may face
bodily harm anyway. The keys are purely to keep prying eyes away from
what they should not see.

Regards,
Eugene