SSH Key Auth funktioniert nicht korrekt

[Zero111]

Ich bin grad am Verzweifeln:

Ich bin grad dabei des SSH Server korrekt einzurichten um an Ende die passwordauth abzuschalten
Putty RSA Keys für beide Serveruser sind erstellt und wurden auch korrekt auf den Server gespeichert


Mit dem Benutzer Root klappt alles Perfekt.

Anmeldung mit SSH Key und puttyagent

Lediglich mit mein normalen User Account will es Partou nicht klappen
Bekomm nur die Meldung "Server refused our key"

Inhalt Verzeichnis .ssh

drwx------  2 zero111 zero111 4096 2011-04-20 17:28 .
drwxr-xr-x 41 zero111 zero111 4096 2011-04-20 17:28 ..
-rw-------  1 zero111 zero111 1675 2011-04-20 16:47 id_rsa
-rw-------  1 zero111 zero111 1011 2011-04-20 17:28 ssh_keys

inhalt der Keyfile:

ssh-rsa AAAAB3NzaC1yc2EAAAABJQAABABU4i3RfRrCnAqu3dpLDiQLftLf+C7LftW1x7rq7X9sIFFaxNBsPvwJ29UMmdYZgiUGuPdBrx113pf9FENHXbRrFMJzY4MALeA9C4RRe6WEyF9lYdtK2pgvbfyBTKtX7ux26T8MRNhK0ah7avo1HyN/XnTrPB3iBXyQPlRZXaax9icGFlQhFhMbPWSf0DIFCo+oNEUkbwEf2lG6uuDStkXEfkHu3mhN8ksF53vMzh5l/ORqaIFeTJ30FY+OhhzhQ4VLHUdcUBO3nfL8MX3o1jM3ztfs1HIetTkH5euOeCFpxhwnDUlA1NXNJ6xVHsfjrFrYCosRH1sOWPMkv3NZQZIIzIB1y9wQWPrUQUjQjfM6DRpoKL55DHL79REHwgpxpw0I7ogMxbGmAOBPYieuxnpGRSiPV+SW4h97FhMJgjNFuoQ33WoAnZusIyD11c8PtNWLAoEST79FT8AsDD+Llyj4tGzrWKcl2uQ5Z1t+HyprYNTXNvC46l3Qr3CnMLmmz7d/YXBdy9ycP0xEmgXZfSQGOUQB6gbTXGJ/YaT5K0xnTxS1cKKlLhWrt/DthWR4f/6+jFcPKQ2GCUCoFKO2nogLGObhO/qN8GvsERYcPeFUuBMF2G2lAaA2bYxVUdsgbIGa5zzq5lkTngZ1LWM8fJZzwbahYoF/NrLRZ+YiWXQwigREWciD1xO9DKFPc+3fuot8jgw2omzBkfWIZfl0svK3XtwC1eCkf5eL+Dpqc5/e+3avM2EJ9/xf4ykfvdB7n7EvnNDp5h2QaAj0sQQBsDeE/AGrUgzc8w9MGOdoRWi3K//XeaSzrWVphgU5M84tCHU6GglRvkqyBILuj5ll9U6ZDLrCS1Q2GCb6KF933+uGMkFtsVjagTtIT7lGKBEwnxVSsmsq0yKmRf7PAsL4wowRD0gnL3RRM7uIwiFJIVCgKpHIsWwgHrP2cAXTbRrzx4iyyDUF92V8h4+NGq+om9MZyHnqOZ0ObZ97dKj949DMTnQFo/05dMNdmF2uX2B+jvm36znLehEK18WX7eA3a2N+AuVwqew/Oih6729UmfrEZzDwz/LoKvW/3GFBSosoAy+r0qC2e1moYq3Njfm8wwX2Up01JjEpihWu6z0xzPRphMPhTn1JNYcomfjLlrJUkEyQC7IzS2LlrHKXFRo4TncGgQWsCe0Mz7/JAUtCkcVEin6xSf7saUNw3NJ2A6ciK2qo7ZCV2RGX4QyVNYRF9aLLUXY998xnSfQLY/Y2KRTIbfFuoBEi1m7tKal1PYyn2SrazLPAKmH/xV5rWs3FOc7CYuhTIEHne6GUyo4et6d/8xZsf5TO7XDL3FZcqxrPIGz5KDlDC46byCPqAGqvwqY9== rsa-key-20110420

die sshd config sieht so aus

# 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/ssh_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

wie gesagt.. Mit Benutzer Root gehts problemlos