hg: added --ssh to specify which SSH binary to use

Thomas Arendsen Hein thomas at intevation.de
Thu Aug 18 23:53:46 CDT 2005


* Perez-Gonzalez, Inaky <inaky.perez-gonzalez at intel.com> [20050818 23:33]:
> >From: Thomas Arendsen Hein
> >2. Or you can just use the file as a ssh key file without making it
> >   executable. Download it, set its permissions to 600, and put it in
> >   ~/.ssh/sshanoncvs. Then add the following to your ~/.ssh/config:
> >
> >   Host cvs.kitenet.net
> >   User cvs
> >   IdentityFile ~/.ssh/sshanoncvs
> >   ForwardAgent no
> >   ForwardX11 no
> >   Compression yes
> >
> >This is what I meant.
> >
> >You can even do:
> >
> >   Host specialaliasonlyforhg
> >   HostName real.hostname.of.hg.repo.example.com
> >   IdentityFile ~/.ssh/sshanoncvs
> >   ...
> 
> Agreed, but multiply by twenty repos that you need to push to twenty 
> different locations, at one different key (and maybe host) each and it 
> becomes a pain to handle manually. Having it redirected to a SSH
> connector
> file (the one that embeds the key on itself) eases management a lot.

Remembering 20 different sshanoncvs commands given each time on the
command line or added each time to each clone of a repo isn't very
comfortable, too. Once you have your preferred setting in
.ssh/config, you can just do copy&paste with only changing few
parts without these (unfortunately needed) chmod tricks.

Thomas

-- 
Email: thomas at intevation.de
http://intevation.de/~thomas/


More information about the Mercurial mailing list