Comment 1 for bug 126911

<lifeless> womble: setup a service account
<lifeless> womble: bzr+ssh://foo@host/.../
<lifeless> womble: with restricted access to only run as that user. If this helps.

Looks like the perfect solution to me :)

bzr://

no authentication

bzr+http://

optional authentication

bzr+ssh://

Strong authentication either for each user or with a dedicated account registering the authorized keys.

We were to *not* manage authentication ourselves. I'll strongly prefer we continue :)

Lowering the importance as I think it's more a documentation problem. Feel free to disagree or bring the discussion to the list.