Package: gokr-rsync
Version: 0.3.3-4
Architecture: amd64
Maintainer: Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
Original-Maintainer: Debian Go Packaging Team <team+pkg-go@tracker.debian.org>
Installed-Size: 15933
Depends: libc6 (>= 2.38)
Static-Built-Using: golang-1.26 (= 1.26.3-2), golang-github-coreos-go-systemd (= 22.6.0-1), golang-github-google-go-cmp (= 0.7.0-1), golang-github-google-renameio (= 2.0.2-1), golang-github-google-shlex (= 0.0~git20191202.e7afc7f-1), golang-github-landlock-lsm-go-landlock (= 0.8.1-1), golang-github-mmcloughlin-md4 (= 0.1.2-1), golang-go.crypto (= 1:0.52.0-1), golang-golang-x-sync (= 0.19.0-1), golang-golang-x-sys (= 0.45.0+dfsg-1), golang-toml (= 1.5.0-1), libcap2 (= 1:2.75-10ubuntu2)
Section: net
Priority: optional
Homepage: https://github.com/gokrazy/rsync
Description: rsync client and daemon, implemented in Go
 gokr-rsync is a native Go implementation of the rsync file transfer
 protocol, wire-compatible with the original tridge rsync (from the Samba
 project) and openrsync (used on OpenBSD and macOS 15+). It implements
 both client and server roles and can send or receive files in either
 direction.
 .
 The same gokr-rsync binary can run as:
  * a one-shot client, similar to rsync(1);
  * a server invoked by a remote rsync(1) client over SSH;
  * a standalone daemon, served either directly on port 873/tcp or
    wrapped in anonymous or authorized SSH.
 .
 On Linux, gokr-rsync sandboxes itself using the Landlock LSM,
 restricting filesystem access to only the source and destination paths
 involved in each transfer. When started as root in daemon mode, it
 additionally enters a mount namespace with the configured rsync modules
 bind-mounted read-only, chroots into it, and drops privileges. These
 layers limit the blast radius of bugs in the protocol handler.
 .
 Example systemd unit and socket files from upstream are installed under
 /usr/share/doc/gokr-rsync/examples/ as a starting point for running
 gokr-rsync as a hardened daemon (DynamicUser, RestrictNamespaces,
 system call filtering, etc.). They are not enabled by default; copy
 them into /etc/systemd/system/ and adjust ExecStart for your modules.
 .
 Note that this implementation is younger and less battle-tested than
 the C rsync from the Samba project; users are encouraged to verify
 their transfers and report discrepancies upstream.
