ssh Connection

Arjun · 07-24-2012, 03:21 AM

Quote:

Originally Posted by xtpeqii

COULD YOU provide us the following content:

content in /etc/ssh/sshd_config

THOUGH YOU'D BETTER ASK SOMEONE WHO USE FEDORA in case of some difference between multiple distros.

Here is the information you are asking for in /etc/ssh/sshd_config

Code:

# Package generated configuration file
# See the sshd_config(5) manpage for details

# What ports, IPs and protocols we listen for
Port 22
# Use these options to restrict which interfaces/protocols sshd will bind to
#ListenAddress ::
#ListenAddress 0.0.0.0
Protocol 2
# HostKeys for protocol version 2
HostKey /etc/ssh/ssh_host_rsa_key
HostKey /etc/ssh/ssh_host_dsa_key
#Privilege Separation is turned on for security
UsePrivilegeSeparation yes

# Lifetime and size of ephemeral version 1 server key
KeyRegenerationInterval 3600
ServerKeyBits 768

# Logging
SyslogFacility AUTH
LogLevel INFO

# Authentication:
LoginGraceTime 120
PermitRootLogin yes
StrictModes yes

RSAAuthentication yes
PubkeyAuthentication yes
#AuthorizedKeysFile	%h/.ssh/authorized_keys

# Don't read the user's ~/.rhosts and ~/.shosts files
IgnoreRhosts yes
# For this to work you will also need host keys in /etc/ssh_known_hosts
RhostsRSAAuthentication no
# similar for protocol version 2
HostbasedAuthentication no
# Uncomment if you don't trust ~/.ssh/known_hosts for RhostsRSAAuthentication
#IgnoreUserKnownHosts yes

# To enable empty passwords, change to yes (NOT RECOMMENDED)
PermitEmptyPasswords no

# Change to yes to enable challenge-response passwords (beware issues with
# some PAM modules and threads)
ChallengeResponseAuthentication no

# Change to no to disable tunnelled clear text passwords
#PasswordAuthentication yes

# Kerberos options
#KerberosAuthentication no
#KerberosGetAFSToken no
#KerberosOrLocalPasswd yes
#KerberosTicketCleanup yes

# GSSAPI options
#GSSAPIAuthentication no
#GSSAPICleanupCredentials yes

X11Forwarding yes
X11DisplayOffset 10
PrintMotd no
PrintLastLog yes
TCPKeepAlive yes
#UseLogin no

#MaxStartups 10:30:60
#Banner /etc/issue.net

# Allow client to pass locale environment variables
AcceptEnv LANG LC_*

Subsystem sftp /usr/lib/openssh/sftp-server

# Set this to 'yes' to enable PAM authentication, account processing,
# and session processing. If this is enabled, PAM authentication will
# be allowed through the ChallengeResponseAuthentication and
# PasswordAuthentication.  Depending on your PAM configuration,
# PAM authentication via ChallengeResponseAuthentication may bypass
# the setting of "PermitRootLogin without-password".
# If you just want the PAM account and session checks to run without
# PAM authentication, then enable this but set PasswordAuthentication
# and ChallengeResponseAuthentication to 'no'.
UsePAM yes
UseDNS no

Wim Sturkenboom · 07-24-2012, 04:00 AM

Is the ssh daemon running?

try the command in bold blue; you should see something like the first line

Code:

wim@webserver:~$ ps -ef |grep sshd
root      3033     1  0  2011 ?        00:00:00 /usr/sbin/sshd
root      6987  3033  0 10:49 ?        00:00:00 sshd: wim [priv]
wim       6989  6987  0 10:49 ?        00:00:00 sshd: wim@pts/0
wim       7004  6990  0 10:50 pts/0    00:00:00 grep sshd
wim@webserver:~$

Or the command posted by chrism01 in post #11 (run as root); again you should see something like the first line that indicates that something (ssh daemon) is listening on port 22

Code:

root@webserver:~# netstat -tanp |grep ssh
tcp6       0      0 :::22                   :::*                    LISTEN     3033/sshd
tcp6       0     52 ::ffff:172.31.208.76:22 ::ffff:172.31.208:59466 ESTABLISHED6987/sshd: wim [pri
root@webserver:~#

Arjun · 07-25-2012, 07:03 AM

Yaa bro.

It is running

I have checked it

Wim Sturkenboom · 07-25-2012, 07:49 AM

I overlooked this in your earlier post #12

Code:

ssh root@127.0.0.1

Code:

Read from socket failed: Connection reset by peer

Try to login as a normal user instead of root. I see that you did allow it in the config but maybe there is something else that blocks it (maybe you did not restart the ssh server after the change?). And in my opinion a security risk.

Once that works, you can use su or sudo to gain root access once your in the system.

chrism01 · 07-25-2012, 08:04 PM

Code:

PermitRootLogin yes

This is definitely a security risk and it is heavily recommended to NOT allow root over ssh.
You might also need to check /etc/hosts.allow, /etc/hosts.deny.
The other thing that can be an issue is the firewall; you can use

Code:

iptables -nvL

# Or

cat /etc/sysconfig/iptables  # RHEL/Fedora

to check