specifying a list of files to transfer

jw schultz jw at pegasys.ws
Wed Jan 15 04:34:01 EST 2003

On Tue, Jan 14, 2003 at 10:15:42PM -0600, Lee Eakin wrote:
> ---begin quoted text---
> > From: jw schultz <jw at pegasys.ws>
> > Date: Tue, 14 Jan 2003 20:07:58 -0800
> > 
> > Nope.  The files-from contents needs to passed on stdin otherwise
> > we would hit command-line length limits.  That is why i'm
> > stressing the fact that allowing paths not within the source
> > or destination trees specified on the command-line would
> > bypass your ssh command= wrapper restrictions.
> > 
> Oh, I see now.  Yes that could be a serious hole.  If the remote command
> included an option (maybe a dummy --files-from) then the ssh wrapper could
> at least abort and notify when it sees it.

If you look at Wayne's description of the patch the remote
command does have a --files-from=- on it's command-line.
However it would be a shame to disable that performance
enhancing facility if we just need sanitize the contents of
the file-from list and require that it only specify paths
relative to the source and dest trees.

I suppose we could allow an option that would permit
unsanitized paths.

	J.W. Schultz            Pegasystems Technologies
	email address:		jw at pegasys.ws

		Remember Cernan and Schmitt

More information about the rsync mailing list