SSH Login

Hi,

Can you please paste your sshd.conf file on your server by removing the origional IP addresses.

#       $OpenBSD: sshd_config,v 1.74 2006/07/19 13:07:10 dtucker Exp $
#       $FreeBSD: src/crypto/openssh/sshd_config,v 1.42.2.4 2006/11/11 00:51:28 des Exp $

# This is the sshd server system-wide configuration file.  See
# sshd_config(5) for more information.

# This sshd was compiled with PATH=/usr/bin:/bin:/usr/sbin:/sbin

# The strategy used for options in the default sshd_config shipped with
# OpenSSH is to specify options with their default value where
# possible, but leave them commented.  Uncommented options change a
# default value.

# Note that some of FreeBSD's defaults differ from OpenBSD's, and
# FreeBSD has a few additional options.

#VersionAddendum FreeBSD-20061110

#Port 1666
Port 22
#Protocol 2
#AddressFamily any
#ListenAddress 0.0.0.0
#ListenAddress ::

# HostKey for protocol version 1
#HostKey /etc/ssh/ssh_host_key
# HostKeys for protocol version 2
#HostKey /etc/ssh/ssh_host_dsa_key

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

# Logging
# obsoletes QuietMode and FascistLogging
#SyslogFacility AUTH
#LogLevel INFO

# Authentication:

#LoginGraceTime 2m
PermitRootLogin yes
#PermitRootLogin forced-commands-only
#StrictModes yes
#MaxAuthTries 6
AllowUsers user1 user2 user3 user4
RSAAuthentication yes
PubkeyAuthentication yes
AuthorizedKeysFile      ~/.ssh/authorized_keys
#AuthorizedKeysFile     .ssh/known_hosts

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

# Change to yes to enable built-in password authentication.
#PasswordAuthentication no
#PermitEmptyPasswords no

# Change to no to disable PAM authentication
#ChallengeResponseAuthentication yes

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

# GSSAPI options
#GSSAPIAuthentication no
#GSSAPICleanupCredentials yes

# Set this to 'no' to disable 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

#AllowTcpForwarding yes
#GatewayPorts no
#X11Forwarding yes
#X11DisplayOffset 10
#X11UseLocalhost yes
#PrintMotd yes
#PrintLastLog yes
#TCPKeepAlive yes
#UseLogin no
#UsePrivilegeSeparation yes
#PermitUserEnvironment no
#Compression delayed
#ClientAliveInterval 0
#ClientAliveCountMax 3
#UseDNS yes
#PidFile /var/run/sshd.pid
#MaxStartups 10
#PermitTunnel no

# no default banner path
#Banner /some/path

# override default of no subsystems
Subsystem       sftp    /usr/libexec/sftp-server

# Example of overriding settings on a per-user basis
#Match User anoncvs
#       X11Forwarding no
#       AllowTcpForwarding no
#       ForceCommand cvs server
                                                       

uetian1707... i have pasted the sshd_config at the hosting server. as for the one on my client box, i couldn't decide which one it is using. as i uncommented the PubkeyAuthentication line but it still pops up the following warning:
PubkeyAuthentication configuration keyword is deprecated. Use AllowedAuthentications.

i had a feeling that this problem is at the client side.

ibu1... i had a read of the article. it is just a general one on how to setup the SSH. my problem however is more complexed than that can offer. first of all the syntax of auth key on freeBSD is different from the one of Debian. you can't have multiple lines on the encrypted code.

uudecode may not be installed and ssh client works only with unscrambled keys then

it was working before: both ssh and scp. then my colleague blocked the root user from sshd_config, then he changed the auth keys. that was where things started going wrong.

it seems like ssh was upgraded. Are you able to log-in?

ssh wasn't upgraded. i wasn't able to log in.

gheist... if you want to help, please read the error messages in the log and tell me how to fix them.

sshd is installed wrongly without Set-UID attribute and only root is able to log in.
Once it was disabled just nobody can log-in.

i have tested it with the root user allowed. it still throws the same error --- therefore, logically you are not correct.

Authentication failure due to scrambled authorized keys file?

gheist... you have seen my auth keys from the previous question. why didn't you say so at the first place? i am afraid your answer is not good enough.

installing uudecode on cpenal lunix is complete solution. FreeBSD has one and uses by default.

the log says all:

warning: PubkeyAuthentication configuration keyword is deprecated. Use AllowedAuthentications.
warning: Unrecognized configuration parameter authorizedkeysfile
warning: Unrecognized configuration parameter subsystem

edit your sshd_config on FreeBSD (the server) to have:
AllowedAuthentications          publickey,password,hostbased

restart your sshd server and try  :-)

i have tried that before. no that didn't fix it. but thanks for the input.

ok let's see. This is what I understood:

you want to connect from linux to a freebsd machine
you created your keys on the linux box.
you copied your keys to the freebsd machine
it is not working.

So let's give a step back and check:
- the use of keys is to avoid using passwords.
- you need to have the private key as id_dsa on your origin linux user ~/.ssh directory
- you need the public key added to the destination user home directory, to the file authorized_keys (maybe if it is freebsd the file can be authorized_keys2)

so if you want to connect from root to root, you need

Linux:
/root/.ssh/id_dsa

FreeBSD:
/root/.ssh/authorized_keys <---- here you copy the content of the id_dsa.pub

I usually do cat id_dsa.pub >> /root/.ssh/authorized_keys   to avoid any fingertip or copy/paste problem.


then you try to ssh from the linux box to the freebsd box, and it should work.

Did you do as described?

Except that FreeBSD's default setting is PermitRootLogin no...