ssh Problem bei public- und private-key in gleichem Verzeichnis

Hallo,
ich habe 2 Computer (einen Server (debian) und einen Client (imac)) und hatte auf beiden den gleichen Benutzer (ID und Name) erstellt. Um mich mittels ssh von Client am Server anzumelden habe ich einfach den public-key auf den Server und den private-key auf dem Client in das jeweilige .ssh-Verzeichnis des Benutzers gelegt.
Ich habe jetzt allerdings meine "Netzwerkstruktur" so geändert, dass das Home-Verzeichnis des Clients auf dem Server liegt und diesem beim Start automatisch auf dem Client gemountet wird.
Seit dem kann ich mich aber nicht mehr mit dem Client am Server anmelden. Ich bekomme folgende Ausgabe:

imac:~ tobe$ ssh -v debian
OpenSSH_4.5p1, OpenSSL 0.9.7l 28 Sep 2006
debug1: Reading configuration data /Network/Servers/<IP-Adresse-des-Rechners>/home/tobe/.ssh/config
debug1: Applying options for debian
debug1: Reading configuration data /etc/ssh_config
debug1: Connecting to debian [<IP-Adresse-des-Rechners>] port 22.
debug1: Connection established.
debug1: identity file /Network/Servers/<IP-Adresse-des-Rechners>/home/tobe/.ssh/id_rsa type 1
debug1: Remote protocol version 2.0, remote software version OpenSSH_3.8.1p1 Debian-8.sarge.6
debug1: match: OpenSSH_3.8.1p1 Debian-8.sarge.6 pat OpenSSH_3.*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_4.5
debug1: Miscellaneous failure
No credentials cache found

debug1: Miscellaneous failure
No credentials cache found

debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-cbc hmac-md5 none
debug1: kex: client->server aes128-cbc hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Host 'debian' is known and matches the RSA host key.
debug1: Found key in /Network/Servers/<IP-Adresse-des-Rechners>/home/tobe/.ssh/known_hosts:1
debug1: ssh_rsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,keyboard-interactive
debug1: Next authentication method: publickey
debug1: Offering public key: /Network/Servers/<IP-Adresse-des-Rechners>/home/tobe/.ssh/id_rsa
debug1: Authentications that can continue: publickey,keyboard-interactive
debug1: Next authentication method: keyboard-interactive
debug1: Authentications that can continue: publickey,keyboard-interactive
debug1: No more authentication methods to try.
Permission denied (publickey,keyboard-interactive).
.

Relevant Pages

  • Re: What doesnt lend itself to OO?
    ... >> proxy and instructs the server to constuct the real object. ... rather than client code. ... If 'clock' is instantiated in the server, ... > for the server interface at the OOA level. ...
    (comp.object)
  • This is going straight to the pool room
    ... or not the client has privilege to do what they're trying to do, ... The server environment is this: ... 3GL User action Routines that Tier3 will execute on your behalf during the ... Routine Name: USER_INIT ...
    (comp.os.vms)
  • [Full-Disclosure] R: Full-Disclosure Digest, Vol 3, Issue 42
    ... Full-Disclosure Digest, Vol 3, Issue 42 ... SD Server 4.0.70 Directory Traversal Bug ... Arkeia Network Backup Client Remote Access ...
    (Full-Disclosure)
  • Re: What doesnt lend itself to OO?
    ... > rather than client code. ... no way to do that without also touching the object with clock semantics ... will not encapsulate both clock semantics and network semantics. ... The server can do whatever it wants ...
    (comp.object)
  • RE: Fax monitor incoming + outgoing calls?
    ... problem between the client computer and the SBS server. ... Client is using the internal IP address of the SBS server as the ... To the folder redirection GPO issue: ...
    (microsoft.public.windows.server.sbs)