[scponly] Problems with rsync and ver 4.6

wby oblyr joe at sublimation.org
Mon Feb 6 14:48:21 EST 2006


Hi Dhiresh,

Thanks for the bug report, this relates to the new getopt processing feature added within the last couple months.  
I will be addressing this shortly.  

Basically, the getopt processor thinks that --server is the same as -s -e -r -v, and since -e is a disallowed 
rsync option, scponly is disallowing the argument.

I'll be working on a fix shortly.

joe

Dhiresh Vyas wrote this message on Mon, Feb 06, 2006 at 14:42 -0500:
> Hi,
> 
> I am trying to use rsync to transfer files over scponly and get the
> following errors in the server log -
> 
> Feb  6 14:32:32 <host> sshd[20423]: Accepted password for user from
> xx.xx.xx.xx port 15708 ssh2
> Feb  6 14:32:32 <host> scponly[20426]: option e is not permitted for use
> with /usr/bin/rsync (arg was rver)(username: user(7000), IP/port:
> xx.xx.xx.xx 15708 22))
> Feb  6 14:32:32 <host> scponly[20426]: requested command (/usr/bin/rsync
> --server --sender -vlogDtpr . /home/user/testfile) tried to use disallowed
> argument (username: user(7000), IP/port: xx.xx.xx.xx 15708 22))
> 
> On the client side, I see -
> 
> rsync: connection unexpectedly closed (0 bytes received so far) [receiver]
> rsync error: error in rsync protocol data stream (code 12) at io.c(359)
> 
> We use scponly 4.6.
> 
> Any help in this matter will be greatly appreciated.
> 
> Regards,
> Dhiresh

> _______________________________________________
> scponly mailing list
> scponly at lists.ccs.neu.edu
> https://lists.ccs.neu.edu/bin/listinfo/scponly




More information about the scponly mailing list