1834149 Members
2387 Online
110064 Solutions
New Discussion

Re: SSH and key

 
SAM_24
Frequent Advisor

SSH and key

Hi,

After I install ssh HP depot version do I need to create any encyption key? I can login using password I believe. Is it necessary creating private/public key? If I create key should I save it in SSH client systems? Please shed some light.

Thanks.
Never quit
4 REPLIES 4
RAC_1
Honored Contributor

Re: SSH and key

ssh authentication can be done in three ways.

1. host based (You define .shosts, /etc/shosts.equiv files and set this to be used in sshd_config files)

2. You create private and public keys and set ssh to exchange it. Public keys is generated and put on the client. ($HOME/.ssh/authorized_keys file)

3. Password based. If you do set any of the above it will authenticate based on password.

Anil
There is no substitute to HARDWORK
Chris Vail
Honored Contributor

Re: SSH and key

Follow the attached instructions. (wow, this is the 2nd time in a couple of minutes I've attached this file!)
Laurie Gellatly
Honored Contributor

Re: SSH and key

Answers to your questions:
>After I install ssh HP depot version do I need to create any encyption key?
NO.
>I can login using password I believe. Is >it necessary creating private/public key?
NO, not necessary.
>If I create key should I save it in SSH >client systems?
I've used the method outlined here:
http://bumblebee.lcs.mit.edu/ssh2/
but you need to decide if you are happy to
have no pass phrase or not and that will
depend on your security risk profile.

HTH ...Laurie :{) 1730
If you're not using OverTime, you're doing overtime!
Andrew Cowan
Honored Contributor

Re: SSH and key

Please Note. From version 3.8 onwards, the default settings in "/etc/ssh/sshd_config" disable password authentication, therefore any inbound connections to a system running this version would have to use key based authentication.

You can revert to the default behaviour by editing the "sshd_config" file and restarting the daemon.

If you need to debug ssh connections use:

ssh -v [-l user_name] host
for outbound connections

and restart the daemon in standalone mode "sshd -d" for inbound.

These options will both show you what is hapenning in real-time.

You should also edit the "/etc/syslog.conf" to catch any other messages from sshd.