On Thu, 26 Sep 2013, Wayne Davison wrote:
The problem you're encountering with rssh is a very old one where it was
rejecting the use of -e combined with --server, which is not correct (the
correct method is to reject any rsync command that doesn't have
--server as the first option, and then no
On Tue, Sep 24, 2013 at 11:43 AM, Andrew Daviel wrote:
> I was trying to use rsync to send files to a fileserver using an rssh
> restricted server.
> It refuses, saying that trying to override the shell with -e is forbidden.
> I didn't type "-e".
>
I should also point out that you can talk to an
On Tue, Sep 24, 2013 at 12:33 PM, Andrew Daviel wrote:
> That's a Perl script to "restrict rsync to subdirectory declared in
> .ssh/authorized_keys".
>
The rrsync is a perl script that limits the user to only running authorized
rsync commands, including restricting options, optionally making it
On Tue, 24 Sep 2013, Kevin Korb wrote:
Maybe you want rrsync instead of rssh? It comes with rysnc.
That's a Perl script to "restrict rsync to subdirectory declared in
.ssh/authorized_keys".
What we want is what rssh does - stop people logging in to a shell prompt,
or running arbitrary com
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Maybe you want rrsync instead of rssh? It comes with rysnc.
On 09/24/13 14:43, Andrew Daviel wrote:
>
>
> I was trying to use rsync to send files to a fileserver using an
> rssh restricted server.
>
> It refuses, saying that trying to override the
I was trying to use rsync to send files to a fileserver using an rssh
restricted server.
It refuses, saying that trying to override the shell with -e is forbidden. I
didn't type "-e".
When I look at the source, I see
/* Checking the pre-negotiated value allows --protocol=29 overrid
