encrypted rsyncd - why was it never implemented?

[Kevin Korb]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

You can run rsyncd over ssh as well.  Either with -e ssh host::module
or you can use ssh's -L to tunnel the rsyncd port.  The difference is
which user ends up running the rsyncd.

On 12/03/2014 12:40 PM, Tomasz Chmielewski wrote:
> rsync in daemon mode is very powerful, yet it comes with one big 
> disadvantage: data is sent in plain.
> 
> The workarounds are not really satisfying:
> 
> 
> - use VPN - one needs to set up an extra service, not always
> possible
> 
> - use stunnel - as above
> 
> - use SSH - is not as powerful as in daemon mode (i.e. read only
> access, chroot, easy way of adding/modifying users and modules
> etc.)
> 
> 
> Why was encrypted communication in rsyncd never implemented? Some 
> technical disagreements? Nobody volunteered?
> 
> 

- -- 
~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~
	Kevin Korb			Phone:    (407) 252-6853
	Systems Administrator		Internet:
	FutureQuest, Inc.		Kevin at FutureQuest.net  (work)
	Orlando, Florida		kmk at sanitarium.net (personal)
	Web page:			http://www.sanitarium.net/
	PGP public key available on web site.
~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEARECAAYFAlR/VEUACgkQVKC1jlbQAQcE+wCfYD+irslnu/nRool4RPL+KjUC
J9wAoKmYNAlfpCMlVKYcV+jpW8e0YNF6
=oUk3
-----END PGP SIGNATURE-----