The password file has to be on both sides.
try
--password-file=/etc/rsyncd.secure
on your command line.
--Mike
At 02:21 PM 11/3/00 -0500, Scott Gribben wrote:
>Hello,
>
>I am working on the initial implementation of rsync here and am having
>trouble getting it to use the "secrets file"
Hello,
I am working on the initial implementation of rsync here and am having
trouble getting it to use the "secrets file" (not prompt for password).
I have the daemon running on the host (rsync -daemon as root), have an
/etc/rsyncd.conf file with 1 module in it, inside the module [Test] I have
2000-11-03-13:02:22 Andy Small:
> 2000-11-02-17:56:56 Bennett Todd:
> > There's been discussion about doing away with this, letting
> > rsync work through something like a depth-first sorted-order
> > traversal or some such, both ends could do that in synch, with
> > memory requirements often down
Thu, 2 Nov 2000 17:56:56, Bennett Todd wrote:
> 2000-11-02-15:17:27 Andy Small:
> > I searched the archive of last 3 months of this list for a FAQ
> > posting, but I could not find one.
>
> I haven't seen such a document, but this mailing list seems to work
> pretty well, and the repetition rate
> converse among themselves. If data is buffered up into blocks they
If you're using zlib on the streams you already *have* sufficient
packetization...
>The data sent over the encrypted channel will usually be
>gzip-compressed, so changing a single byte won't produce a single byte
>change in decompressed plaintext. (It might be appropriate to force
>at least -z0 if --privacy is specified.) Simple corruption of the
>stream will be detected by gz
