./sysutils/tarsnap, Secure online backup service

[ CVSweb ] [ Homepage ] [ RSS ] [ Required by ] [ Add to tracker ]


Branch: CURRENT, Version: 1.0.37, Package name: tarsnap-1.0.37, Maintainer: pkgsrc-users

Tarsnap is a secure online backup service for BSD, Linux, OS X,
Solaris, Cygwin, and can probably be compiled on many other UNIX-like
operating systems. The Tarsnap client code provides a flexible and
powerful command-line interface which can be used directly or via
shell scripts.


Master sites:

SHA1: 5c3b97ec82a0c94c35ae27b1b8422fc192735781
RMD160: 3491143e0272ea610a11179582d326ec4764842a
Filesize: 614.697 KB

Version history: (Expand)


CVS history: (Expand)


   2016-03-10 23:54:13 by Thomas Klausner | Files touched by this commit (2) | Package updated
Log message:
Update tarsnap to 1.0.37.

First the new release: Tarsnap 1.0.37 is now available.  This version brings
the following substantive changes compared to tarsnap 1.0.36:

 * tarsnap-key(gen|mgmt|regen) now accept a --passphrase-time option,
which specifies the duration to be spent on computing the derived keys
used for encrypting the tarsnap key file.

 * tarsnap now accepts a --keep-going option when deleting or printing
statistics about multiple archives.

 * tarsnap-keymgmt now accepts a --print-key-permissions option for
listing the permissions contained in a key file.

 * tarsnap --print-stats now accepts a --csv-file option for printing
statistics in comma-separated-value format.

 * tarsnap now accepts a --verify-config command which exits silently
after checking the configuration file(s) for syntax errors.

 * tarsnap now looks for a server named "v1-0-0-server.tarsnap.com"
instead of the historic "betatest-server.tarsnap.com" hostname.  This
should have no user-visible effect in most configurations.

 * tarsnap now correctly warns if a sparse extract fails due to hardlinks.

 * tarsnap now prints a warning if creating an empty archive.

As usual, there are also many minor build fixes, harmless bug fixes, and code
refactoring / cleanup changes.  For a full listing of changes, consult the
tarsnap git repository: https://github.com/Tarsnap/tarsnap
   2016-03-05 12:29:49 by Jonathan Perkin | Files touched by this commit (1813) | Package updated
Log message:
Bump PKGREVISION for security/openssl ABI bump.
   2015-11-04 02:32:42 by Alistair G. Crooks | Files touched by this commit (499)
Log message:
Add SHA512 digests for distfiles for sysutils category

Problems found with existing digests:
	Package memconf distfile memconf-2.16/memconf.gz
	b6f4b736cac388dddc5070670351cf7262aba048 [recorded]
	95748686a5ad8144232f4d4abc9bf052721a196f [calculated]

Problems found locating distfiles:
	Package dc-tools: missing distfile dc-tools/abs0-dc-burn-netbsd-1.5-0-gae55ec9
	Package ipw-firmware: missing distfile ipw2100-fw-1.2.tgz
	Package iwi-firmware: missing distfile ipw2200-fw-2.3.tgz
	Package nvnet: missing distfile nvnet-netbsd-src-20050620.tgz
	Package syslog-ng: missing distfile syslog-ng-3.7.2.tar.gz

Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden).  All existing
SHA1 digests retained for now as an audit trail.
   2015-08-21 20:03:22 by Thomas Klausner | Files touched by this commit (2) | Package updated
Log message:
Update to 1.0.36.1:
OS X lacks the POSIX-mandated clock_gettime function, and tarsnap is
not using libcperciva's "support broken operating systems" compatibility
mechanism yet.  Add -DPOSIXFAIL_CLOCK_REALTIME to the build.
   2015-08-21 16:43:17 by Thomas Klausner | Files touched by this commit (2) | Package updated
Log message:
Update to 1.0.36:

1. SECURITY FIX: When constructing paths of objects being archived, a buffer
could overflow by one byte upon encountering 1024, 2048, 4096, etc. byte
paths. Theoretically this could be exploited by an unprivileged user whose
files are being archived; I do not believe it is exploitable in practice,
but I am offering a $1000 bounty for the first person who can prove me wrong:
http://www.daemonology.net/blog/2015-08 … ounty.html

2. SECURITY FIX: An attacker with a machine's write keys, or with read keys
and control of the tarsnap service, could make tarsnap allocate a large
amount of memory upon listing archives or reading an archive the attacker
created; on 32-bit machines, tarsnap can be caused to crash under the
aforementioned conditions.

3. BUG FIX: Tarsnap no longer crashes if its first DNS lookup fails.

4. BUG FIX: Tarsnap no longer exits with "Callbacks uninitialized" when
running on a dual-stack network if the first IP stack it attempts fails to
connect.

5. tarsnap now avoids opening devices nodes on linux if it is instructed to
archive /dev/.  This change may prevent "watchdog"-triggered reboots.

6. tarsnap -c --dry-run can now run without a keyfile, allowing users to
predict how much Tarsnap will cost before signing up.

7. tarsnap now has bash completion scripts.

8. tarsnap now takes a --retry-forever option.

9. tarsnap now automatically detects and uses AESNI and SSE2.

As usual, there are also many minor build fixes, harmless bug fixes, and code
refactoring / cleanup changes.  For a full listing of changes, consult the
tarsnap git repository: https://github.com/Tarsnap/tarsnap
   2014-08-21 18:02:11 by Jonathan Perkin | Files touched by this commit (1)
Log message:
Fix build on SunOS (needs explicit -lnsl).
   2014-04-02 14:04:50 by Thomas Klausner | Files touched by this commit (2) | Package updated
Log message:
Update to 1.0.35:

Changes since version 1.0.34:

   A bug in tarsnap 1.0.34 which could cause tarsnap to crash
   (segmentation fault or bus error) when encountering network
   glitches or outages is fixed.

   When tarsnap encounters "insane" filesystems (procfs and other
   similar synthetic filesystems which are not reasonable to
   archive), it now archives the filesystem mount point but by
   default does not recurse into the filesystem. Previous releases
   (since 1.0.26) did not archive the synthetic filesystem mount
   point.

Changes since version 1.0.33:

   Tarsnap now supports both IPv4 and IPv6.

   Tarsnap is now more resilient against short network glitches
   when it first connects to the Tarsnap server.

   Tarsnap now supports platforms with mandatory structure alignment
   (e.g., ARM OABI).

   Tarsnap now restores terminal settings if killed with ^C while
   reading a password or passphrase.

   Multiple minor bug fixes and cleanups.
   2014-02-26 19:20:29 by Sebastian Wiedenroth | Files touched by this commit (1)
Log message:
Bulk build wants openssl