On Tue, 2006-01-24 at 22:45 -0600, Johnny Hughes wrote:
On Tue, 2006-01-24 at 21:18 -0700, Craig White wrote:
On Tue, 2006-01-24 at 22:08 -0600, Les Mikesell wrote:
On Tue, 2006-01-24 at 21:35, Craig White wrote:
thanks for checking...it remains untouched from distribution
# grep Protocol /etc/ssh/sshd_config #Protocol 2,1
Obviously, I had one issue and it was a real problem identifying it.
But it still doesn't make any sense. Installing freenx should put the key in authorized_keys2 and sshd should use it from there.
I can tell you for sure though that I did this on 2 different CentOS 4 installs - and the same solution applied made things work fine.
You must be doing something else that affects sshd. It should default to protocol 2 and prefer the authorized_keys2 file.
To be honest - I have other fish to fry and working is good.
As for doing something else that affects sshd...
It's possible - I did change one setting - trying to fix the issue...
# grep Pubkey /etc/ssh/sshd_config PubkeyAuthentication yes
which previously had been commented out - this was a desperation move and I never set it back. If this would cause this behavior, then I can rectify it (later).
the next option down is this:
AuthorizedKeysFile .ssh/authorized_keys
it is normally remarked out .. if that is set, you can only have .ssh/authorized_keys and .ssh/authorized_keys2 won't work.
---- trust me when I tell you this is unchanged from distribution
[root@srv2 ~]# grep AuthorizedKeys /etc/ssh/sshd_config #AuthorizedKeysFile .ssh/authorized_keys
Craig