We have a server with rssh-2.2.3 on CentOS 3, and tried connecting with 
rsync-3.0.6 from CentOS 5.

I get "insecure -e option not allowed".
When I look a the source for rsync, I find it's adding "-e.s" for some 
reason but I can fix that by using --protocol=26.

I tried building the current version of rssh (2.3.4-1) thinking that maybe 
the problem was fixed. But it's actually worse.

I don't know why rsync is sending "--sender" etc., but it's the standard 
RedHat version of rsync. I'm guessing that rssh is not parsing long options 
properly and is just finding 'e' in --server.

Seeing as rsync is one of the documented commands that works with rssh, 
I'm wondering what's going on.


$ rsync -vv  andrew@myserver:public_html/two/try2.html .
opening connection using: ssh -l andrew trshare rsync --server --sender -vve.s 
. public_html/two/try2.html

illegal insecure e option
This account is restricted by rssh.
Allowed commands: scp sftp rsync


$ rsync -vv --protocol=26  andrew@myserver:public_html/two/try2.html .
opening connection using: ssh -l andrew trshare rsync --server --sender -vv . 
public_html/two/try2.html

illegal insecure e option



-- 
Andrew Daviel, TRIUMF, Canada
Tel. +1 (604) 222-7376  (Pacific Time)

------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk
_______________________________________________
rssh-discuss mailing list
rssh-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rssh-discuss

Reply via email to