On Fri, Aug 18, 2006 at 09:42:32AM -0700, Mike McMullen wrote: > 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 [...] > 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? It is on the order of random-typewriter monkeys producing Hamlet that this particular issue could happen from a bad RPM -- but it is *quite* likely that it could happen if your system were hacked and someone clumbsily installed a trojaned sshd. What happens if you run "rpm -V openssh"? And, uh, I'd also run chkrootkit. -- Matthew Miller mattdm@xxxxxxxxxx <http://mattdm.org/> Boston University Linux ------> <http://linux.bu.edu/> -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
