A non-text attachment was scrubbed...
Name: rsync-ssl.patch
Type: text/x-patch
Size: 27004 bytes
Desc: OpenSSL patch for rsync-cvs.
Url :
http://lists.samba.org/archive/rsync/attachments/20031012/b3ed1f7b/rsync-ssl.bin
-------------- next part --------------
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi.
I've been hacking together a way to use rsync with OpenSSL, and have
attached my current patch against a recent CVS tree. The details of
this implementation are:
1. The SSL code is added as a "layer" that is forked into its own
process.
2. An SSL connection is established by the client issuing the
command:
#starttls
And, if the server allows SSL, it replies with
@RSYNCD: starttls
At which point both sides begin negotiating the SSL connection.
Servers that can't or don't want to use SSL just treat it as a
normal unknown command.
3. The SSL code is meant to be unobtrusive, and when this patch is
applied the program may still be built with no SSL code.
4. There are a number of details not implemented.
All warnings apply; I don't do C programming all that often, so I
can't say if I've left any cleanup/compatibility errors in the code.
Also: <http://rsync.samba.org/lists.html> refers to the (now gone)
smart-questions document on tuxedo.org, which should now be catb.org.
Cheers,
- --
Casey Marshall || rsdio@metastatic.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.7 <http://mailcrypt.sourceforge.net/>
iD8DBQE/ih9xgAuWMgRGsWsRAp8RAJ0XyONLiOSDgHHAOBRNO6sZ/P2dRwCeKfu8
LEvhhkUglOm3xMyrdJT4u9Q=aT/N
-----END PGP SIGNATURE-----
