[scponly] Re: Problems with rsync and ver 4.6

[Paul Hyder]

The scponly code checks the rsync arguments to stop unsafe options.
In this case it doesn't like the "--server" option.  Looks like
the getopt is parsing this as an unsafe -e.

It would help to know the operating systems on the scponly server and
client host, which version of rsync this is, and for you to verify that
the rsync command used was as is shown below.
    Paul Hyder
    NOAA Earth System Research Laboratory, Global Systems Division
    Boulder, CO

Jakub Suchy wrote:
> Hi,
> 
> i just wanted to know, if you have any progress with this issue? I just
> downloaded scponly and am having same problems...
> 
> Feb 28 09:56:46 ns sshd[30105]: Accepted publickey for makro_student
> from ::ffff:XXX port 60716 ssh2
> Feb 28 08:56:48 ns scponly[30134]: option e is not permitted for use
> with /usr/bin/rsync (arg was rver)(username: makro_student(1251),
> IP/port: ::ffff:XXX 60716 22))
> Feb 28 08:56:48 ns scponly[30134]: requested command (/usr/bin/rsync
> --server -vvvlogDtprz --delete . /files/) tried to use disallowed
> argument (username: makro_student(1251), IP/port: ::ffff:XXX
> 60716 22))
> 
> using latest scponly from source @ CentOS 4.2, glibc-2.3.4-2.13
> 
> Thanks
>