On Fri, Sep 27, 2002 at 04:19:45PM +0100, Tim Haynes wrote: > > I'd agree with your assessment that it's picking up the wrong ssh-keygen, > as I was thinking that by the time you suggested it :) > > > Let's assume, for the moment, that it's remote machine :-) > > chmod 000 `which ssh-keygen` > > sshd -p somehighnumber22 > > apt-get install ssh > > At least that way you still have either the old or possibly even the new > sshd listening on 22, and a backup entry-point if you need it.
That's brilliant. I like it a lot. But I also found the *real* problem... Whenever I did a chmod 000 `which ssh-keygen`, I was just making sure this had the desired effect... ls -l `which ssh-keygen` lrwxrwxrwx 1 root root 11 Nov 15 1999 /usr/local/bin/ssh-keygen -> ssh-keygen1 I thought that was kinda strange, so I checked it out on another potato machine. ls -l `which ssh-keygen` -rwxr-xr-x 1 root root 81884 Jun 26 23:29 /usr/bin/ssh-keygen Turns out the problematic machine had this 'ssh-keygen1' installed in /usr/local/bin *as well as* ssh-keygen in /usr/bin - so I removed the link to ssh-keygen1, and tried reinstalling the new package. Everything went swimmingly :-) > I'd recommend the middle step every time you're about to play with the ssh > package as a precaution on a remote machine anyway (unless you're lucky > enough to have a serial console toy). Thanks for the tip! Cheers, Simon. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
