Commit graph

3 commits

Author SHA1 Message Date
riz
afe7739fd1 Update tarsnap to version 1.0.31.
Changes since version 1.0.30:

	- A race condition in key generation has been fixed which could
	  allow a newly-generated key file to be read by another local
	  user if the key file is being generated in a world-readable
	  directory and the user running tarsnap-keygen has a umask other
	  than 0066.
	- A bug in key generation has been fixed which could allow a
	  newly-generated key file to be read by another local user
	  if they key file is being generated in a world-writable
	  directory (e.g., /tmp).
	- Tarsnap now supports Minix.
	- Tarsnap now ignores blank lines in key files; line-buffers
	  its output (which makes tarsnap --list-archives | foo more
	  responsive); and prints a progress indicator during tarsnap --fsck.
	- Multiple minor bug fixes.
2011-12-03 07:09:31 +00:00
wiz
ca383c3a7a Update to 1.0.30. Drop maintainership since I never actually used it...
Changes since version 1.0.29:

    A bug fix in the handling of readdir errors; in earlier versions,
    it was theoretically possible for a failing hard drive or other
    errors in reading directories to result in files being silently
    omitted from an archive.

    Several bug fixes relating to the handling of @archive directives
    with mtree files.

    A bug fix to prevent cache directory corruption resulting in
    tarsnap failing if it was interrupted at exactly the right
    (wrong) moment in its operation.

    A bug fix to correctly handle ~ in tarsnap -s path substitutions.

    Many more minor bug fixes.
2011-08-25 15:24:14 +00:00
wiz
ae49ad647e Follow Greg's advice and reimport in a better place, i.e. move
tarsnap from security to sysutils.
2011-05-15 11:16:14 +00:00