Using non-default SSH keys

[Martin Reitbauer]

Hi,

I was wondering if there is a way to make Cervisia use an SSH key in a
non-default location (i.e. outside ~/.ssh/). The thing is that my
default ssh key has got a passphrase on it, and I hate entering it over
and over again when using Cervisia. So I created a separate one without
a passphrase, but I can't find out how to make Cervisia (or command-line
cvs for that matter) use it.

I tried entering "ssh -i ~/path/to/non-default-key/" into the "Use
remote shell" field in the repository options, but to no avail.

I'd appreciate any pointers..

best,
Martin
_______________________________________________
Cervisia mailing list
Cervisia@...
https://mail.kde.org/mailman/listinfo/cervisia

Hi Martin,

On Thursday 05 June 2008, Martin Reitbauer wrote:

> Hi,
>
> I was wondering if there is a way to make Cervisia use an SSH key in
> a non-default location (i.e. outside ~/.ssh/). The thing is that my
> default ssh key has got a passphrase on it, and I hate entering it
> over and over again when using Cervisia. So I created a separate one
> without a passphrase, but I can't find out how to make Cervisia (or
> command-line cvs for that matter) use it.
>
> I tried entering "ssh -i ~/path/to/non-default-key/" into the "Use
> remote shell" field in the repository options, but to no avail.
>
> I'd appreciate any pointers..

Do you know ssh-agent? Start it with your desktop session, add your keys
to it (you've to enter your passphrases) and after that you can use ssh
without entering the passphrase again.

This works for console AND GUI applications.


Cheers,
André
_______________________________________________
Cervisia mailing list
Cervisia@...
https://mail.kde.org/mailman/listinfo/cervisia

On Thursday 05 June 2008, Martin Reitbauer wrote:
> Wow! Worked like a charm, thank you so much! I'm actually going to be
> punching in more code than passphrases now :)

:-)

> But since this works out so well, I'm a bit confused by this part of
> the manual, which I had googled up earlier in the process:
>
> "Note that Cervisia cannot answer possible password requests from the
> server machine. You must make sure that a remote login works without
> requiring you to enter the password. With plain vanilla rsh, this can
> be achieved for example by creating a .rhosts file in your home
> folder with a list of trusted hosts (see the rsh manpage).
> With ssh, it can be achieved by copying your public key located in
> the file identity.pub, located in the $HOME/.ssh/ folder to the
> server. In this case, the key must not be encrypted with a passphrase
> (see the ssh manpage and the CVS/SSH FAQ on SourceForge). If you are
> unsure about these issues, ask your system administrator"

Probably outdated.

> Should this part be updated?

Yep, a note about ssh-agent would be a good idea.


Cheers,
André
_______________________________________________
Cervisia mailing list
Cervisia@...
https://mail.kde.org/mailman/listinfo/cervisia