[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Tarsnap 1.0.30 "bug bounty edition" is now available. This new version brings
a long list of bug fixes, mostly reported as part of the four month old Tarsnap
Bugs fixed in 1.0.30 include:
* If Tarsnap fails to read a directory while creating an archive (e.g., due to
a failing hard disk) it could silently skip some files.
* If Tarsnap cannot access the directory from which it was launched (e.g., due
to a failing hard disk or permissions on the directory changing) and multiple
directories are specified to be archived, Tarsnap could archive the wrong paths.
* If the @archive directive is used with an mtree archive, Tarsnap could hang.
* The ~ character was incorrectly handled in substitution targets using the -s
* If the Tarsnap process was killed at exactly the right (wrong) moment after
creating or deleting an archive, its cache directory could enter a state where
future Tarsnap operations would immediately fail with an error.
* Over 200 less significant issues, ranging from spelling errors in source code
comments to incorrect handling of dates billions of years prior to the Big Bang.
The new release is available from the usual location:
Many thanks to all the people who reported bugs in Tarsnap, and especially to
Ralph Corderoy, who managed to find a total of 140 issues.
Security Officer, FreeBSD | freebsd.org | The power to serve
Founder / author, Tarsnap | tarsnap.com | Online backups for the truly paranoid