2017-11-11 - firstname.lastname@example.org
- Update to version 1.0.39
- Changes since 1.0.38
* Fix a division-by-zero crash when reading corrupt password-encrypted tarsnap
* Fix a crash in reading corrupt "cpio newc" format archives included via the
tarsnap @archive directive, on 32-bit systems.
* Fix a bug in the handling of corrupt "ar" format archives included via the
tarsnap @archive directive.
* Fix an abort trap which complained about files with a negative modification
time. (This assertion occured after the archive is stored, so no user data
was at risk.)
- Changes since 1.0.37
* tarsnap now accepts an --initialize-cachedir command, which is intended for
the GUI and is not needed for command-line usage.
* tarsnap now applies --humanize-numbers to the SIGINFO "progress" output.
* tarsnap now gives a warning for --configfile /nosuchfile.
* tarsnap now accepts --iso-dates, which prints file and directory dates as
yyyy-mm-dd hh:mm:ss in "list archive" mode. This can be cancelled with
* the ./configure --with-conf-no-sample flag causes in the sample config file
to be installed as tarsnap.conf instead of tarsnap.conf.sample. This may
result in overwriting an existing tarsnap.conf file.
* tarsnap now accepts --force-resources to force the decryption of a
passphrase-encrypted key file to proceed even if it is anticipated to require
an excessive amount of memory or CPU time. This can be cancelled with
* tarsnap now supports OpenSSL 1.1.
* tarsnap now displays 'Deleting archive "foo"' when deleting a single archive
in verbose mode. (The former behaviour was to print that message only when
multiple archives were being deleted by a single tarsnap command.)
* tarsnap now accepts --archive-names filename, which reads a list of
archive names from a file in addition to any -f options.
2016-07-31 - email@example.com
- 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
* 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
* 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.
* tarsnap -c --dry-run can now run without a keyfile,
allowing users to predict how much Tarsnap will cost before
* Tarsnap now includes bash completion scripts.
* Tarsnap now automatically detects and uses AESNI and SSE2
- clean spec file