Obviously ssh is a source of a large fraction of the problems people have in using rsync. Most of the problems seem to come from the fact that we have to run an external program, and so we get lockups because of operating system or rsync bugs in blocking/nonblocking pipes/sockets etc. I'm looking at adding built-in stream encryption, so that we can give people some privacy even if they can't use ssh. In combination with the challenge-response password system, this will mean that both passwords and rsync data will be protected from snooping on the wire. I'm not trying to recreate all of ssh, so it won't be appropriate for really secret data. It also won't protect against active attacks (DNS spoofing, tcp takeover, etc). But for mid-level security I think it will help -- perhaps for backups of home directories and that kind of thing. Anybody interested? -- Martin Pool Church of tridge
- I also am getting hang/timeout using rsync 2.4.6 -e s... ian stanley
- Re: I also am getting hang/timeout using rsync 2.... Neil Schellenberger
- Re: I also am getting hang/timeout using rsyn... ian stanley
- Re: I also am getting hang/timeout using rsync 2.... Andrew Tridgell
- Re: I also am getting hang/timeout using rsync 2.... Harry Putnam
- Re: I also am getting hang/timeout using rsync 2.... Dave Dykstra
- Re: I also am getting hang/timeout using rsync 2.... Harry Putnam
- Re: Builtin encryption support in rsync (was ... Martin Pool
- Re: Builtin encryption support in rsync (... Martin Pool
- Re: Builtin encryption support in rsy... Martin Pool
- Re: Builtin encryption support i... Martin Pool
- Re: Builtin encryption support in rsy... Martin Pool
- Re: I also am getting hang/timeout using rsyn... Bennett Todd
- Re: I also am getting hang/timeout using rsync 2.... Dave Dykstra
- Re: I also am getting hang/timeout using rsyn... Harry Putnam