Connexion SSH = root ok mais pas user !

Support Debian
#1

Bonsoir,

Sur mon client, il n’y a que root qui puisse se connecter en ssh au serveur (même réseau…)
En user le message est le suivant :

et depuis root:

root@lagache:/home/irena# ssh sabrina@192.168.1.9 -p 58420 sabrina@192.168.1.9's password: Linux lagache 2.6.32-5-686 #1 SMP Mon Mar 26 05:20:33 UTC 2012 i686

Mon cat /etc/ssh/sshd_config côté client (IDEM côté serveur…) (ip : 192.168.1.10) :

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

# What ports, IPs and protocols we listen for
Port 58420
# Use these options to restrict which interfaces/protocols sshd will bind to
#ListenAddress ::
ListenAddress 192.168.1.10
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 no
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 yes
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
#2

Salut,

Le mode debug serait plus parlant …

#3

Petite remarque, tu authentifie par clé privée ( option mdp commentée )

mais tu laisse

Essai de commenter usePAM, et crée un couple de clé pour ton user.

#4

[quote=“loreleil”]Salut,

Le mode debug serait plus parlant …

Pas mieux comme compréhension (MON USER ) :

irena@lagache:~$ ssh sabrina@192.168.1.9 -p 58420 OpenSSH_5.5p1 Debian-6+squeeze1, OpenSSL 0.9.8o 01 Jun 2010 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug2: ssh_connect: needpriv 0 ssh: Could not resolve hostname 192.168.1.9:58420: Name or service not known

#5

Salut,

J’irai bien voir du côté de /etc/hosts, hostname, et peut être bien resolv.conf … :083

Pas toi … :033

#6

Même root ne peux plus se connecter…

Alors pourquoi le SFTP (via GNOME en tapant : ssh://monuser@sonip:58420 ) :violin: fonctionne ?