- Update to version 1.0.39
- Changes since 1.0.38
  * Fix a division-by-zero crash when reading corrupt password-encrypted tarsnap
    key files.
  * 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
    --no-iso-dates.
  * 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
    --no-force-resources.
  * 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.)

• Files Changed
• Browse Source