If you can't let root in, how about running it as a daemon? One end is already acting
as root to initiate it, so make the other end a daemon, already waiting for the
incoming connection. If you need ssh to get through a firewall or something, set up a
redirect as non-root, I don't have ssh handy (i'm deep inside an intranet that I don't
control), so i don't remember the syntax for redirects, but you'd redirect port 873
(or another, if you moved it) on the remote system to appear to be port 8730 or
something on your local machine. Then, you just rsync -a --port=8730
localhost::whateveryoucallthemodulefor/ whereveryouwanttoputitonthelocalmachine.
The security on rsyncd isn't all that great - plaintext passwords - but in this
implementation, they're never going over the wire in plaintext. It's in ssh over the
wire, and the plaintext is then over the loopback interface to the remote host's port.
If possible, make the rsyncd on the read side. It works for writing, but i've heard
it's not as solid.
Tim Conway
[EMAIL PROTECTED]
303.682.4917
Philips Semiconductor - Colorado TC
1880 Industrial Circle
Suite D
Longmont, CO 80501
"There are some who call me.... Tim?"
