Hello list

I'm trying to get around a problem with rsync and protocol 30.
I found out that if I try to do rsync over rssh with protocol 30, this is not working.
Command:
rsync rsshsynctest usr@vmsrv01:.
(It is equal to
rsync --protocol=30 rsshsynctest usr@vmsrv01:.
)
--------------
Error:

insecure -e option not allowed.
This account is restricted by rssh.
Allowed commands: rsync

If you believe this is in error, please contact your system administrator.

rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(601) [sender=3.0.7]
--------------
Log:
Feb 21 15:02:15 vmsrv01 rssh[15395]: insecure -e option in rdist command line!
Feb 21 15:02:15 vmsrv01 rssh[15395]: user batch attempted to execute forbidden commands
Feb 21 15:02:15 vmsrv01 rssh[15395]: command: rsync --server -e.Lsf . .
--------------

If I do the command
rsync --protocol=29 rsshsynctest usr@vmsrv01:.
(Or also rsync --protocol=29 rsshsynctest -e ssh usr@vmsrv01:. )
It works fine.

To me it is interesting because -e is disabled anyway, I thought.
And it's alos embarrassing to me that I can use -e unless the used protocol is > 29. I read that all protocols < 30 in rsync do their hashes with md4, but protocols > 29 do them with md5. Does that matter?

Any idea?

Attachment: binm9CZi8VUmx.bin
Description: PGP Public Key

Attachment: pgpPJX2GlTPUg.pgp
Description: PGP Digital Signature

------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
rssh-discuss mailing list
rssh-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rssh-discuss

Reply via email to