rsync - Jan 2019 - --server options

Hi all,

I see a couple of earlier threads, particularly this one:

https://www.mail-archive.com/rsync at lists.samba.org/msg32328.html

partly answer my question, but not fully.

I also am writing a wrapper, so that I can run multiple dirvish runs
against the same server, using forced commands, but without using
multiple keys to get multiple commands, which is my current workaround.

But in the interests of locking things down, I'd like to know what the
options are in the -eSTRING section, so I can choose which to
allow/force. Is that documented anywhere? Or do I have to resort to the
source?

And/or can I safely assume that anything in the -eSTRING won't let a
client get any more than I intended? Does the STRING just run from after
the -e to the next whitespace?

Thanks,

Richard

On 21/01/19 8:07 PM, Richard Hector via rsync wrote:
> Hi all,
> 
> I see a couple of earlier threads, particularly this one:
> 
> https://www.mail-archive.com/rsync at lists.samba.org/msg32328.html
> 
> partly answer my question, but not fully.
> 
> I also am writing a wrapper, so that I can run multiple dirvish runs
> against the same server, using forced commands, but without using
> multiple keys to get multiple commands, which is my current workaround.
> 
> But in the interests of locking things down, I'd like to know what the
> options are in the -eSTRING section, so I can choose which to
> allow/force. Is that documented anywhere? Or do I have to resort to the
> source?
> 
> And/or can I safely assume that anything in the -eSTRING won't let a
> client get any more than I intended? Does the STRING just run from after
> the -e to the next whitespace?
Anybody? Are these options/flags deliberately kept obscure?

Cheers,
Richard

I don't remember your original question but if I didn't suggest looking
at rrsync I should have.  It comes with rsync in the contrib dir and it
knows which options to allow/deny and it can restrict the transfer to a
specific dir and read-only or write-only.  Since it comes with rsync it
is kept current with the options rsync uses including the undocumented ones.

Even if it doesn't do exactly what you are trying to do, it is a perl
script so it should be easy enough to modify for your needs.  Just keep
a diff so you can easily analyze changes in new versions.

On 2/7/19 10:57 PM, Richard Hector via rsync wrote:
> On 21/01/19 8:07 PM, Richard Hector via rsync wrote:
>> Hi all,
>>
>> I see a couple of earlier threads, particularly this one:
>>
>> https://www.mail-archive.com/rsync at lists.samba.org/msg32328.html
>>
>> partly answer my question, but not fully.
>>
>> I also am writing a wrapper, so that I can run multiple dirvish runs
>> against the same server, using forced commands, but without using
>> multiple keys to get multiple commands, which is my current workaround.
>>
>> But in the interests of locking things down, I'd like to know what
the
>> options are in the -eSTRING section, so I can choose which to
>> allow/force. Is that documented anywhere? Or do I have to resort to the
>> source?
>>
>> And/or can I safely assume that anything in the -eSTRING won't let
a
>> client get any more than I intended? Does the STRING just run from
after
>> the -e to the next whitespace?
> 
> Anybody? Are these options/flags deliberately kept obscure?
> 
> Cheers,
> Richard
> 
> 
-- 
~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,
	Kevin Korb			Phone:    (407) 252-6853
	Systems Administrator		Internet:
	FutureQuest, Inc.		Kevin at FutureQuest.net  (work)
	Orlando, Florida		kmk at sanitarium.net (personal)
	Web page:			https://sanitarium.net/
	PGP public key available on web site.
~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: OpenPGP digital signature
URL:
<http://lists.samba.org/pipermail/rsync/attachments/20190207/8dbbca2c/signature.sig>