Maybe different ssh-versions? I had problems connecting between SuSE
Open-SSH and SSH2-Debian. Best is to have the same ssh everywhere. It
should be sufficient to check it in sshd-configs, pam-adjustment is IMHO
not necessary.
Oh, and of course don't forget to exchange the public keys!
h2h
zelko
Dale Amon schrieb:
I've an application that needs a secure automatic login
from an application program, between particular accounts
on particular machines.
I know this used to work (a few years ago!) but I
am having difficulty this time around getting it going.
I'm using a public key for the connection, with null
password given when asked by the ssh-keygen.
The destination machine accepts that the publickey
is valid but asks for a passphrase nonetheless. It
doesn't accept a return for null password either, it
falls back on normal password log in.
As I said, I've not done this particular set up in,
oh, 6 years, so I would not be surprised if there
were changes in the debian defaults for sshd, pamd,
the way ssh handles things etc, etc.
A suggestion or three would be appreciated.
--
--
Schrack Energietechnik GmbH
IT Services
Tel.: +43(0)1/866 85 - DW 650
Fax.: +43(0)1/866 85 - DW 1635
======= Der Spruch des Tages lautet: =======
BOFH excuse #44:
bank holiday - system operating credits not recharged
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
