Hi, Where are you generating your key pair? Where are you installing your public key? Generate you key pair on the host you wish to login "from". Install the public key on the host you wish to login "to". rob@from-host:~> ssh-keygen -t dsa -C 'rob@from-host' rob@to-host:~> scp rob@from-host:~/.ssh/id_dsa.pub .ssh/authorized_keys This will copy over ssh the public key created on the from-host into the .ssh/authorized_keys file on the to-host. There is no need to restart the sshd server. On Thu, Apr 14, 2005 at 02:35:54AM +0200, Robert Rozman wrote:

Hi,

I have problems setting up rsa based ssh access to suse 9.2 machine.

I did this:

ssh-keygen -t dsa -C 'root@voipy' cat .ssh/id_dsa.pub >> .ssh/authorized_keys

and then corrected /etc/ssh/sshd_config (at the end of email). I did /etc/init.d/sshd restart and I can still log in in old fashioned way with username and password.... I can login also with private key (but it asks for normal user password instead of passphrase of the key??), but I'd like to eliminate old fasioned way...

What am I doing wrong ?

Thanks in advance,

regards,

Rob.

-----------------------------------------------sshd_config----------------------------------------------------------------

$OpenBSD: sshd_config,v 1.69 2004/05/23 23:59:53 dtucker 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 #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 yes #StrictModes yes #MaxAuthTries 6

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 yes # 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 yes #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

-- Check the headers for your unsubscription address For additional commands, e-mail: suse-security-help@suse.com Security-related bug reports go to security@suse.de, not here

-- -ashley Did you try poking at it with a stick?