Secure Shell Paper

[Steven E. Protter]

I'm looking for something comprehensive dealing with such things as passphrases and public key exchange.

I wonder if I need to exchange public keys for two machines on the same subnet. I'd like to read a comprehensive documents.

It's worth 10 points to the winner. :-)

[Kellogg Unix Team]

Start from http://www.openssh.org/

...Manjeet

[Christian Gebhardt]

I heard that some people are still reading books ;-)
http://www.oreilly.com/catalog/sshtdg/

Chris

[linuxfan]

Hi Steven,

Check these out

SSH FAQ
http://www.employees.org/~satch/ssh/faq/ssh-faq.html

Here are some good articles on key management in SSH.
Part I - http://www-106.ibm.com/developerworks/library/l-keyc.html
Part II - http://www-106.ibm.com/developerworks/library/l-keyc2/
Part III - http://www-106.ibm.com/developerworks/library/l-keyc3/

Not sure if this answer's your question or not, but hope it helps.

-Ramesh

[Steven E. Protter]

Thank you gentlemen. I have investigated the links and assigned a few points. When I get a few minutes, I will read in depth and try the documents. More points will be assigned if one of them lets me do what I want, which is to use scp to transfer files without a password or passphrase.

I obvioiusly want whatever I do to be completely secure, which is why I'm not using rcp.

Steve

[linuxfan]

Hi Steven,

If you are looking to do scp without passphrase or password then you would need some manual set up.

The articles i provided actually tell you how to run keychain script http://www.gentoo.org/proj/en/keychain.xml
which starts the ssh-agent on your system. Note: The ssh-agent(script) would need to be started everytime the system reboots.

You would however need to generate your ssh-keys (man ssh-keygen)and distibute them to your remote systems.

Once you have set up your keys correctly, start the ssh-agent by running the keychain script and sourcing the file(created by keychain) you should be able to run ssh commands and copy files/directories using scp without providing any password/passphrase.

-HTH
Ramesh

[John Payne_2]

You want what you do to be completely secure...

Do you really want completely secure, or 'very well protected'? I never consider ssh to be 'completely secure', but you get reasonably good protection out of it, provided you continually upgrade as version to fix vulnerabilities come out...

We are moving to a VPN solution here for our administrative machines, which allows the encyption needed for god protect, but you can use the good old programs like rcp, rexec, telnet, and ftp without worrying about passwords and data being seen.

I guess you get what you pay for there.

I have found the O'rielly book: "SSH, the secure shell : the definitive guide" a very good source for how to do things with ssh like what you are asking for.

Hope it helps

John

[Steven E. Protter]

Bad choice of words.

Completely secure means nobody can get passwords in clear text. In this context. This is a firewall protected network and there is currently no need for outsiders like me to get in from outside. For that we have "secure" dial in.

Steve

[Chris Wong]

Hi,

I have 4 SSH (HP specific articles) here:

http://newfdawg.com/SHP-Articles.htm

- Chris

[Kevin Wright]

wonder if I need to exchange public keys for two machines on the same subnet. I'd like to read a comprehensive documents.

If you want to be authenticated with your pbulic keys, you need to add your .pub file to the authorized_keys file on the other host. To automatically be authenticated without supplying a passphrase, create your passphrase to be null.