openrsync imported into the tree

Contributed by rueda on 2019-02-11 from the diving-into-base dept.

openrsync, a clean-room implementation of rsync, is being developed by Kristaps Dzonsons as part of the rpki-client(1) project [featured in an earlier article]. openrsync(1) has been imported into the tree (as "rsync") by Sebastian Benoit (benno@):

CVSROOT:	/cvs
Module name:	src
Changes by:	benno@cvs.openbsd.org	2019/02/10 16:18:28

Added files:
	usr.bin/rsync  : Makefile TODO.md blocks.c child.c client.c 
	                 downloader.c extern.h fargs.c flist.c hash.c 
	                 io.c log.c main.c md4.c md4.h mkpath.c 
	                 receiver.c rsync.1 rsync.5 rsyncd.5 sender.c 
	                 server.c session.c socket.c symlinks.c 
	                 uploader.c 

Log message:
Import Kristaps' openrsync into the tree.
OK deraadt@

The "Security" section on the GitHub site contains a description of openrsync's use of OpenBSD's security features.

At the time of writing, rsync is not yet linked to the build.

(Comments are closed)

Comments

By thomasw_ (thomasw_) thomas.wildeman@gmail.com on 2019-02-11 15:32 http://www.flickr.com/photos/thomasw_/

Very thankful for this development.
By Billy Larlad (billylarlad) on 2019-02-11 17:16

This is very welcome! Thanks to everyone involved.

rsync is versatile, but the downside is that it definitely has <em>a lot</em> of options: its compressed manual page is almost as big as the compressed openrsync sources. I'm really excited about an rsync clone that I can actually sort of understand. (That said, I am hopeful that at least one rsync feature -- exclude -- can make it into openrsync.)

Again, thanks!
By Renaud Allard (renaud) renaud@allard.it on 2019-02-11 18:26

rsync in base. Excellent.
Thank you Kristaps and benno
By anexit (anexit) bannereddivpool@gmail.com on 2019-02-13 19:17

Fantastic!
By Janne Johansson (jj) jj@stacken.kth.se on 2019-02-17 10:12 http://www.inet6.se

If there ever was a single pkg I always add to all obsd boxes, it would be rsync.
By chas (chas) on 2019-02-19 18:47

I usually push rsync over stunnel with a self-signed key on both sides that is checked with verify=4, so I am less fearful of hostile network data. I launch stunnel with inetd or socket activation, on one side with client=yes.

If the rsync protocol were being redesigned today, implicit chroot and setuid under libtls would likely be the default.

Latest Articles

Mon, Oct 07
- 20:42 OpenBSD 7.6 Released (1)
Wed, Sep 25
- 11:09 Major change to sysupgrade(8) behaviour (0)
Tue, Sep 24
- 16:38 OpenBSD -current is now "7.6-current" (0)
- 10:57 OpenBSD now enforcing no invalid NUL characters in shell scripts (0)
- 09:21 EuroBSDCon 2024 presentations (0)
Mon, Sep 23
- 18:02 rpki-client 9.3 released (0)
Sat, Sep 21
- 18:11 OpenSSH 9.9 released! (0)
Fri, Sep 20
- 15:41 OpenBGPD 8.6 released (0)
Wed, Sep 18
- 05:22 OpenBSD -current has moved to version 7.6 (0)

Credits

Copyright © 2004-2008 Daniel Hartmeier. All rights reserved. Articles and comments are copyright their respective authors, submission implies license to publish on this web site. Contents of the archive prior to April 2nd 2004 as well as images and HTML templates were copied from the fabulous original deadly.org with Jose's and Jim's kind permission. This journal runs as CGI with httpd(8) on OpenBSD, the source code is BSD licensed. undeadly \Un*dead"ly\, a. Not subject to death; immortal. [Obs.]