bzr_access installation and usage

[Eugene Wee]

Hi,

On Sun, Oct 18, 2009 at 4:28 AM, Vincent Ladeuil <v.ladeuil+lp at free.fr> wrote:
> You specify all the identify files you need (the keys you need
> for the all repos you want to access) in your ~/.ssh/config file
> and they will be tried until one succeeds.
>
> You use the key to enter the repo, no key, no repo, from there,
> bzr_access limits your access or not, then your committer id is
> really identifying you as the one creating the revisions you
> push, so any key is good.

Okay, after trying it out, I now remember the problem I had in mind
when I stated that "with multiple repositories, I will need either
multiple key pairs or multiple user accounts" last night. The problem
is that the repository (collection) has to be provided as an argument
to bzr_access so bzr_access can find the appropriate bzr_access.conf
file. This means that if I have more than one repository, they all
have to be under the same repository collection, and a user with
access to one has access to all. As such, if I have another shared
repository repo3, and I want to allow alice access to repo1 and repo3,
I cannot stop her from also accessing repo2 if my setup only has one
user account and one key pair per user.

For now, it seems to me that if you have unrelated projects and want
to simplify things for your users, you are best off with a user
account for each project, and one key pair per user.

Regards,
Eugene