Tarsnap - Online backups for the truly paranoid

Navigation menu

Downloading Tarsnap

At the present time, pre-built binaries are not available for Tarsnap — it must be compiled from the source code. Some operating systems include Tarsnap packages (e.g., the FreeBSD Tarsnap port, NetBSD Tarsnap port), which automate the compiling and installation process.

If you wish to compile manually,

  1. Download the latest source tarball and SHA256 hash file (below).
  2. Proceed to Compiling Tarsnap.

Latest Tarsnap release

Tarsnap (August 20, 2015)


Changes since version 1.0.35:

  • A theoretically exploitable one-byte buffer overflow when archiving objects with long path names is fixed.
  • A vulnerability which allowed a corrupt archive to cause tarsnap to allocate a large amount of memory upon listing archives or reading the corrupt archive is fixed.
  • Tarsnap no longer crashes if its first DNS lookup fails.
  • Tarsnap no longer exits with "Callbacks uninitialized" when running on a dual-stack network if the first IP stack it attempts fails to connect.
  • tarsnap -c --dry-run can now run without a keyfile, allowing users to predict how much Tarsnap will cost before signing up.
  • Tarsnap now includes bash completion scripts.
  • Tarsnap now automatically detects and uses AESNI and SSE2 cpu features.

Changes since version 1.0.36:

  • Tarsnap now works around an OS X standards-compliance bug which was making tarsnap fail to build.

Other Tarsnap code

  • Old releases are available for historical and diagnostic purposes, but we strongly recommend that people use the latest official tarball.
  • The Tarsnap git repository is on github; developers may wish to watch changes in progress or investigate bugs.