On Saturday 05 February 2005 03:53, David Corbin wrote:
> The box in question is publicly accessible. Why have another port open if
> I don't need to? Besides, I can't get rsyncd to start correctly, so I was
> looking for alternatives.
Can't check from here, but probably you can use ssh or stunnel to tunnel rsync
connections to the server inside ssl. This way, you still have to have rsyncd
running on the server, but can restrict incoming connections to localhost
(ie, the server itself) only, and close rsync port (873 IIRC) to the rest of
the world.
HTH
--
Absolutely nothing should be concluded from these figures except that
no conclusion can be drawn from them.
-- Joseph L. Brothers, Linux/PowerPC Project
--
[email protected] mailing list
