- Update to version 1.0.37
- Changes since 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.
- Changes since 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.