Find the answer to your Linux question:
Results 1 to 4 of 4
Hi all, Can anyone help me with sshd on suse - I'm not sure whether I've got it set up right... i'm trying to test it by logging in locally, ...
  1. #1
    Linux Newbie
    Join Date
    Nov 2006
    Posts
    123

    sshd

    Hi all,
    Can anyone help me with sshd on suse - I'm not sure whether I've got it set up right...
    i'm trying to test it by logging in locally, but I get
    Code:
    benscomputer:/home/ben # ssh localhost
    The authenticity of host 'localhost (127.0.0.1)' can't be established.
    RSA key fingerprint is 8c:08:ca:6a:4a:94:28:1e:cf:1a:78:f1:3d:ff:5b:f0.
    Are you sure you want to continue connecting (yes/no)? yes
    Warning: Permanently added 'localhost' (RSA) to the list of known hosts.
    Password:
    Password:
    Password:
    Permission denied (publickey,keyboard-interactive).
    benscomputer:/home/ben # man sshd_config
    Reformatting sshd_config(5), please wait...
    it never asks for username, just password - and it fails no matter whether I put ben's password in or root's.

    My /etc/ssh/sshd_config is as thus:
    Code:
    #	$OpenBSD: sshd_config,v 1.72 2005/07/25 11:59:40 markus 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.
    
    Port 22
    #Protocol 2,1
    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_rsa_key
    #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 no
    StrictModes yes
    MaxAuthTries 4
    
    #RSAAuthentication yes
    #PubkeyAuthentication yes
    #AuthorizedKeysFile	.ssh/authorized_keys
    
    # 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
    
    # To disable tunneled clear text passwords, change to no here!
    PasswordAuthentication no
    PermitEmptyPasswords no
    
    # Change to no to disable s/key passwords
    #ChallengeResponseAuthentication yes
    
    # Kerberos options
    #KerberosAuthentication no
    #KerberosOrLocalPasswd yes
    #KerberosTicketCleanup yes
    #KerberosGetAFSToken no
    
    # GSSAPI options
    #GSSAPIAuthentication no
    #GSSAPICleanupCredentials yes
    
    # Set this to 'yes' to enable support for the deprecated 'gssapi' authentication
    # mechanism to OpenSSH 3.8p1. The newer 'gssapi-with-mic' mechanism is included
    # in this release. The use of 'gssapi' is deprecated due to the presence of 
    # potential man-in-the-middle attacks, which 'gssapi-with-mic' is not susceptible to.
    #GSSAPIEnableMITMAttack no
     
    
    # 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 mechanism. 
    # Depending on your PAM configuration, this may bypass the setting of 
    # PasswordAuthentication, PermitEmptyPasswords, and 
    # "PermitRootLogin without-password". If you just want the PAM account and 
    # session checks to run without PAM authentication, then enable this but set 
    # ChallengeResponseAuthentication=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
    
    # no default banner path
    #Banner /some/path
    
    # override default of no subsystems
    Subsystem	sftp	/usr/lib/ssh/sftp-server
    
    # This enables accepting locale enviroment variables LC_* LANG, see sshd_config(5).
    AcceptEnv LANG LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE LC_MONETARY LC_MESSAGES 
    AcceptEnv LC_PAPER LC_NAME LC_ADDRESS LC_TELEPHONE LC_MEASUREMENT 
    AcceptEnv LC_IDENTIFICATION LC_ALL

  2. #2
    Linux Engineer Zelmo's Avatar
    Join Date
    Jan 2006
    Location
    Riverton, UT, USA
    Posts
    1,001
    The big difference I'm seeing between your sshd_config and mine is that the RSAAuthentication and PubkeyAuthentication lines are commented out in yours, but not in mine. I don't know which of those is significant (assuming one or both is), but it's something to try.
    Stand up and be counted as a Linux user!

  3. #3
    Linux Enthusiast
    Join Date
    Apr 2004
    Location
    UK
    Posts
    658
    Code:
    benscomputer:/home/ben # ssh localhost
    That hash implies that you are running ssh as root. By default ssh will use the current username as the login for the remote system. Pair this with:

    Code:
    PermitRootLogin no
    And ssh will reject the root login.

    try

    Code:
    ssh ben@localhost
    and use your "ben" password.

    Let us know how you get on.

    Chris...
    To be good, you must first be bad. "Newbie" is a rank, not a slight.

  4. #4
    Linux Newbie
    Join Date
    Nov 2006
    Posts
    123
    Quote Originally Posted by kakariko81280
    That hash implies that you are running ssh as root. By default ssh will use the current username as the loginf for the remote system. Pair this with:
    oh does it, cheers - I didn't know that!
    Thanks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
...