keychain support in SuSE?
Are there any plans to include keychain in an upcoming SuSE version? Introductory description: << One of OpenSSH's more intriguing features is its ability to authenticate users using the RSA and DSA authentication protocols, which are based upon a pair of complementary numerical "keys". And one of the main appeals of RSA and DSA authentication is the promise of being able to establish connections to remote systems without supplying a password. The keychain bash script makes handling RSA and DSA keys both convenient and secure. It acts as a front-end to ssh-agent, allowing you to easily have one long-running ssh-agent process per system, rather than per login session. This dramatically reduces the number of times you need to enter your passphrase from once per new login session to once every time your local machine is rebooted.
Here is more info about keychain: http://www.gentoo.org/projects/keychain/ --jeroen
* Jeroen W. Pluimers (All I'M) wrote on Thu, Apr 18, 2002 at 10:28 +0200:
<< The keychain bash script makes handling RSA and DSA keys both convenient and secure. It acts as a front-end to ssh-agent,
Hum. I don't think that this is important, but I really don't like to have a shell script as front end for some very security relevant tool...
allowing you to easily have one long-running ssh-agent process per system, rather than per login session.
Hum?! What should this help? To save some memory (needed for YaST2 - SCNR.)?
This dramatically reduces the number of times you need to enter your passphrase from once per new login session to once every time your local machine is rebooted.
ARGHH! The key should be cleared *at least* when you're leaving the workstation, since someone other could use your shell. And in the night, when nobody uses an ssh connection, why should it be available? And when I log off and a colleguage logs on on this local workstation, why the heck should my key be in the memory of that workstation?! This was why I don't think such a feature make sense. But surprisingly you will notice, that the ssh-agent can be used in that way without any shell script. If ssh-agent is startet, just make sure that you have it's PID & Co, you can easily write it into a file. But for most purposes it's enough to launch ssh agent with X. I launch it by a menu entry with a new terminal. oki, Steffen -- Dieses Schreiben wurde maschinell erstellt, es trägt daher weder Unterschrift noch Siegel.
participants (2)
-
Jeroen W. Pluimers (All I'M) -
Steffen Dettmer