> I have added hostbased authentication to the sesnor's config file and
> set up tcp wrappers to allow the analysis station access. I added the
> analysis station to the sensor's .rhosts (and .shosts FWIW). I put the
> public key file of the analysis station user over in root's ~/.ssh2 on
> the sensor and created the authorizations file. Also generated a key
> pair for root on the sensor.
> 
> But I must still be missing something because it still asks me to enter
> the root password. This is on ssh 2.0.13.
> 

I too have tried and failed with this. Several months after giving up,
there was an announcement about the 2.1.0 beta as below, which mentions
that this is one of 2.0.13's many bugs that is fixed in 2.1: 
 
> There is a new beta version of SSH Secure Shell 2.1 available at
> http://www.ssh.com .
> 
> This version has already been tested widely internally, but before the
> actual release we'd like you to try and test this evaluation
> version. Any feedback will be greatly appreciated.
> 
> There is also a new (March 1) Windows client beta available, which can
> be found in the same location (http://www.ssh.com).
> 
> Unix version ChangeLog summary (compared to ssh-2.0.13):
> 
> --clip clip--
> ...
>  
> 1999-11-12  Sami Lehtinen  <[EMAIL PROTECTED]>
> 
>         * Changed behaviour of '-f' parameter in ssh2. Now, if specified,
>           implies '-S' (client doesn't request session channel, ie. tty from
>           server), and client doesn't die if a locally forwarded channel is
>           closed. The listener stays there, waiting for
>           connections. Persistent forwarding works only with ssh-2.1.0 and
>           newer servers (older servers incorrectly close the
>           command-channel). With optional 'o' argument (specified '-fo' on
>           the command-line), goes to one-shot mode, which is the same
>           behaviour as before (ie. as soon as forwardings close, client
>           exits).
>         
>         * Fixed authentication code bugs. Should now work. Even with
>           hostbased. And with the order "hostbased,publickey,password".
> --end of clip---

The updated ssh FAQ also now has various workarounds for this bug:
http://www.tigerlair.com/ssh/faq/ssh-faq-3.html#ss3.5

HTH
-- 
Simon Dalley CEng MIEE, [EMAIL PROTECTED]
tel +44 (0) 1235 816206

Reply via email to