Need help on bazaar..

[Tata Dano]

Hi Eugene,

Thank you so much for sharing this information and experience. Though, we
are still encountering some problems with regards in pushing and updating
bazaar on the remote and local repo we are still looking at this
possibility. About the ssh-keygen that I am talking about was generated by
mtn (monotone), but I wonder if it can be used over bazaar. But if it will
place inside .ssh/authorized_keys then maybe it will do.

But if things will not turn out right on this scheme then the last possible
option would be to use a human gatekeeper. I think most of the issues we are
encountering today will be addressed on this method.

Thank you once again.

Sincerely,

Tata

On Mon, Oct 19, 2009 at 1:37 PM, Eugene Wee <crystalrecursion at gmail.com>wrote:

> Hi,
>
> On Mon, Oct 19, 2009 at 11:09 AM, Tata Dano <dano at i360connect.com> wrote:
> > I already got some resource how to generate rsa keys on Windows machines
> > since most of our co-workers are working on it.
>
> I am not sure what you found, but I use PuTTY:
> http://www.chiark.greenend.org.uk/~sgtatham/putty/<http://www.chiark.greenend.org.uk/%7Esgtatham/putty/>
>
> However, if I am not wrong, private keys generated on PuTTY (using
> PuTTYgen) can be password protected, but exporting them to a non-PuTTY
> format loses password protection. If password protection of the
> private key is important to you, you could use ssh-keygen on Linux to
> generate the keys, then import them for use on PuTTY. Of course, if
> you are only ever going to use PuTTY, then this is just unnecessary
> work.
>
> > I also do some research on
> > "contrib/bzr_access" but unable to point it directly. Can you help me
> > provide the link how to set this up? And, is it applicable also to run it
> on
> > CentOS machines?
>
> You can find contrib/bzr_access in the source code available from
> bazaar-vcs.org:
> http://bazaar-vcs.org/SourceDownloads
> It is a Python script that you should be able to run if you are able
> to run Bazaar itself, thus it should work on CentOS.
>
> The script comes with documentation. If you are as clueless as me, you
> might want to note that the restricted access comes from the use of
> the command option in the .ssh/authorized_keys file for the user
> account on your server, and the usernames in the bzr_access.conf file
> should correspond to the usernames specified in the command option
> strings in .ssh/authorized_keys. The protocol used is bzr+ssh, but the
> paths are relative to the directory specified for the given user in
> .ssh/authorized_keys. For example, if the entry for alice specifies
> /home/bzr/repo1 as the directory, then to branch /home/bzr/repo1/trunk
> alice will run:
> bzr branch bzr+ssh://bzr@example.com/trunk
>
> Regards,
> Eugene
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ubuntu.com/archives/bazaar/attachments/20091019/e4eb9479/attachment.htm