I am going to upgrade the rest of my boxes to 10.0 (even though I don't
like it much) so I have computability. Then I will attack this SSH thing
again from there.
G.Chinnery.
Jim Cheetham wrote:
G Chinnery wrote:
correct again. remaned it to authorized_keys and now its got
owner/group max and rw-r--r-- perms. I never noticed the owner/group
b4 I guess that is wrong?
Nope, that seems to be fine.
bash-2.05$ ssh -v -l max apollo uname -a
OpenSSH_2.9p2, SSH protocols 1.5/2.0, OpenSSL 0x0090602f
This seems to be an older version of OpenSSH, which in itself isn't a
problem, except that I'm not seeing the debug lines that I wanted ...
debug1: read PEM private key done: type DSA
debug1: read PEM private key done: type RSA
debug1: identity file /var/www/.ssh/identity type -1
debug1: identity file /var/www/.ssh/id_rsa type 1
debug1: identity file /var/www/.ssh/id_dsa type -1
Seems to indicate that only the id_rsa file exists, and that it is OK
debug1: Encryption type: blowfish
debug1: Sent encrypted session key.
debug1: Installing crc compensation attack detector.
debug1: Received encrypted confirmation.
debug1: Doing password authentication.
[EMAIL PROTECTED]'s password:
I'm surprised that there is no debug information about offering the
key files. Perhaps it's a version thing.
Can you log in to apollo as the apache user, without being asked for
password? If not, then perhaps apollo's ssh server is not accepting
the use of public keys, and we'll have to poke around in it's
configuration. If yes, then can you do (as apache) 'ssh -v apollo' so
I can compare the debug lines? Possibly also try 'ssh -vvv apollo' to
get more (too much?) debug data, I'd really like to be able to see
which authentication methods are being considered internally ...
Basically, if public key authentication works for 'apache' and doesn't
work for 'max', the problem *should* be related to the permissions of
the .ssh directory, and the files in it.
-jim
