On Fri, Aug 18, 2006 at 08:45:04AM -0700, Mike McMullen wrote:
I updated a few of my servers recently with yum. After I did that,
my automated rsyncs to servers stopped working. The updated
servers are refusing the publickeys I've used for months and months.
[...]
Aug 18 08:35:14 mail sshd[25419]: Parsing authorization file
/root/.ssh2/authorization resulted in error (user root tried to
authenticate)
[...]
The version of sshd on the remote server is
"SSH Secure Shell SSH-1.99-OpenSSH_3.8p1 Debian 1:3.8p1-3 (non-commercial
version) on i686-pc-linux-gnu".
What confuses me is why it says Debian. I use the out of the box yum
configuration so everything
should be for a FC4 configuration.
Are you positive you are connecting to the machine you think you are? Since
you show a log message from the remote machine, presumably you can connect
with some other form of authentication, yeah? What do you get if you do "rpm
-q openssh" on that machine?
--
Hi Matthew,
Thank you for your response. Yes, I am positive I'm on the correct machine. All the
production servers I have are running FC4. I have some development boxes running
FC5. There is only Fedora in our shop. No Debian.
Here is the weird part. I did an "rpm -q openssh" on a server that the publickeys still
work with and got:
openssh-4.2p1-fc4.10
I then did it on one of the servers that has the ssh2 directory and doesn't accept
publickeys and got the same thing:
openssh-4.2p1-fc4.10
However if I do an "sshd -v" on the server where publickeys work I get:
OpenSSH_4.2p1, OpenSSL 0.9.7f 22 Mar 2005
When I do this on a server where the keys don't work I get:
sshd: SSH Secure Shell SSH-1.99-OpenSSH_3.8p1 Debian 1:3.8p1-3 (non-commercial version) on
i686-pc-linux-gnu
Both report the same rpm but it appears sshd is different in each one.
Again, I only use the out of the box repos for updates.
Is it possible I got a bad rpm?
If so, how can I correct this?
Thanks for your help,
Mike
