I have dropbear server working successfully with rssh now.  The problem 
lay in where dropbear was expecting the sftp-server binary.

(Note: the following paths are as per installed on Debian Sarge - things 
are probably different on other systems) 

The openssh package has sftp-server at /usr/lib/openssh/sftp-server and 
a symlink from /usr/lib/sftp-server to there.  The openssh daemon and 
rssh expect and call the /usr/lib/openssh version, whilst dropbear is 
calling it at /usr/lib - dropbear works fine with this normally, but as 
soon as rssh is brought into the picture, rssh (appropriately) refuses 
to accept the unexpected binary location.

Specifying the sftp-server location on the sftp client commandline makes 
it acceptable to rssh, like this:
   $ sftp -s /usr/lib/openssh/sftp-server [EMAIL PROTECTED]


James Shewey wrote:
> Is it a client or a server? 

It has client and server parts.  I am using only the server portion at 
present.  In terms of comparing memory usage of dropbear server and 
openssh server, this is what top reports:

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND            
                                  
 1725 root       8   0  1796 1796 1472 S  0.0  0.3   0:00.00 sshd               
                                   
 1645 root       8   0   592  592  504 S  0.0  0.1   0:00.01 dropbear           
                                   

Karl.

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
rssh-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/rssh-discuss

Reply via email to