Siduction Forum

Siduction Forum => Software - Support => Thema gestartet von: hightime in 2014/06/07, 17:46:05

Titel: How to set up ssh keys at login
Beitrag von: hightime in 2014/06/07, 17:46:05
What is the preferred way to set up ssh keys at login? In the past I've used something like this in either .bashrc or .profile:
keychain --quiet ~/.ssh/id_rsa With siduction this doesn't seem to be working. I also tried to use keychain's eval feature as mentioned in its man page. That didn't work either.

I get the prompt for my passphrase, but no keys are loaded.

Dan


Titel: Re: How to set up ssh keys at login
Beitrag von: piper in 2014/06/08, 00:26:43
https://wiki.debian.org/SSH
https://www.debian.org/devel/passwordlessssh
http://sshmenu.sourceforge.net/articles/key-setup.html
Titel: Re: How to set up ssh keys at login
Beitrag von: hightime in 2014/06/08, 21:28:31
Thanks, but those are all links to general information on installing and setting up an ssh client. My question is about keychain.

With Redhat, Archlinux and even my old Aptosid box you can add a couple of lines to .bash_profile, as per the keychain man page, to launch keychain at login. It calls ssh-askpass if it's a GUI login to prompt for your passphrase and add your keys to ssh-agent.

I've done some more experimenting and it appears that with lightdm as the login manager .bash_profile is not even being called. Is there some setting that controls this?  If I switch to using kdm it does call .bash_profile, but the keychain - ssh-askpass part is not working.

And to clarify my original post, if I do a console login -- no GUI desktop -- the keychain - ssh-askpass process works correctly.

Is anyone successfully using keychain with siduction linux?
Titel: Re: How to set up ssh keys at login
Beitrag von: melmarker in 2014/06/10, 21:52:55
only a wild guess - the files you are mention are bash - debian uses dash as sh - in that case the profile would be $HOME/.profile

EDIT: i was wrong with my wild guess - but there is a good explanation here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636108