Up to [cvs.NetBSD.org] / pkgsrc / sysutils / tarsnap
Request diff between arbitrary revisions
Keyword substitution: kv
Default branch: MAIN
tarsnap: Requires e2fsprogs on Linux. Identified by drecklypkg ci on CentOS 7 and recent Ubuntu.
tarsnap: update to 1.0.41. ### Tarsnap 1.0.41 (March 21, 2025) - tarsnap now has mitigations to defend against information leakage via chunking: Chunks are padded using the PADME scheme, and small-alphabet cycles are prohibited in chunking to block a chosen-plaintext attack. - tarsnap -c now accepts --dry-run-metadata, which simulates creating an archive without reading any file data. This is significantly faster than a regular --dry-run, and is suitable for checking which filesystem entries will be archived (with -v) or checking the total archive size (with --totals or --progress-bytes). - tarsnap now accepts --noatime with -c mode, which requests that the operating system does not update atime when reading files or directories. Not supported by all operating systems or filesystems. - If the server-side state was modified and tarsnap exits with an error, it will now have an exit code of 2. - tarsnap will read a config file in $XDG_CONFIG_HOME/tarsnap/tarsnap.conf; or ~/.config/tarsnap/tarsnap.conf if $XDG_CONFIG_HOME is not set. The previous config file ~/.tarsnaprc is still supported, and will not be deprecated. - tarsnap now accepts --null-input as a synonym for --null. For compatibility reasons, --null is still supported, and will not be deprecated. - tarsnap now accepts --null-output, which causes --list-archives to separate each archive name with a null character (like `find -print0`). If one or more -v arguments are specified, multiple null characters are used to separate fields; see the man page for details. - tarsnap now accepts --null-output with -x and -t, which causes them to separate each filename with a null character. If there are multiple fields on a line, null characters are used instead of spaces; see the man page for details. - tarsnap now accepts --null-output with --print-stats, which causes it to separate fields and lines with null character(s); see the man page for details. - tarsnap now accepts --hashes, which causes --list-archives to print hashes of archive names. If one or more -v arguments are specified, it will print other metadata (as per --list-archives). This option is intended for the GUI and is not needed for command-line usage. - tarsnap now accepts -f TAPEHASH with --list-archives --hashes, which prints metadata about the specified archive(s). Multiple -f options may be specified. This option is intended for the GUI and is not needed for command-line usage. - Fixed a problem with strict aliasing if somebody compiled with gcc11 or higher using -O3, does not have SSE2, and is using a passphrase-protected keyfile.
*: bump for openssl 3
tarsnap: update to 1.0.40.
Tarsnap 1.0.40 is now available. This version brings several improvements
compared to tarsnap 1.0.39:
* tarsnap now accepts a --resume-extract option to skip extracting files whose
filesize and mtime match existing files on disk.
* tarsnap now accepts --progress-bytes SIZE, which prints a progress message
after each SIZE bytes are processed, up to once per file. This can be
disabled with --no-progress-bytes.
* tarsnap now accepts a --passphrase method:arg option which accepts:
* --passphrase dev:tty-stdin
* --passphrase dev:stdin-once
* --passphrase dev:tty-once
* --passphrase env:VARNAME
* --passphrase file:FILENAME
* tarsnap now accepts a --dump-config option to print the command-line and all
non-blank lines read from config files.
* tarsnap now exits with an error if there are unused command-line arguments.
(i.e. "tarsnap -d -f a1 a2", where "a2" is unused.)
* Improved performance on some x86, amd64, and arm64 systems by using
cryptographic instruction set extensions.
* When sent SIGINFO or SIGUSR1, tarsnap now prints the number of files and the
number of uncompressed bytes processed, in addition to the previous output.
* A zsh completion file can be installed with
configure --with-zsh-completion=DIR.
As usual, there are also lots of minor build fixes, harmless bug fixes, and
code cleanups.
Support PKG_SYSCONFDIR. Bump PKGREVISION.
*: Recursive revision bump for openssl 1.1.1.
Updated tarsnap to 1.0.39. Tarsnap 1.0.39 is now available. (Yes, just 2 weeks after 1.0.38.) This version brings several important bug fixes: * tarsnap 1.0.38 (but not earlier versions) would exit with an assertion failure after successfully creating an archive containing a file with a "last modified" time prior to January 1st, 1970. * tarsnap 1.0.38 and earlier could crash if instructed to archive the contents of corrupt cpio or ar archives (via the @archive directive). * tarsnap 1.0.38 and earlier could crash if passed an invalidly encrypted key file.
Updated tarsnap to 1.0.38. Tarsnap 1.0.38 is now available. This version brings several new features compared to tarsnap 1.0.37: * Tarsnap now supports OpenSSL 1.1. * tarsnap accepts an --iso-dates option, which causes times to be printed in YYYY-MM-DD HH:MM:SS format rather than the traditional unix "ls -l" style. * tarsnap accepts a --force-resources option to proceed with decryption of a passphrase-encrypted key file even if it is anticipated to use an excessive amount of memory or CPU time. (This may be useful if tarsnap inaccurately estimates the amount of memory your system has available.) * tarsnap accepts an --archive-names <file> option, which reads a list of archive names to operate on when operating in -d and --print-stats modes. (This should make some scripts simpler; no more need to construct a command line which has '-f' inserted before each archive name.) Potentially (but unlikely) breaking changes in this code compared to tarsnap 1.0.37: * tarsnap now applies the --humanize-numbers option to the "progress" output printed by SIGINFO / SIGUSR1. If you have scripts which send signals to tarsnap and parse its output, they may need to be updated. * tarsnap -v now prints 'Deleting archive "foo"' even if only one archive is being deleted. If you have scripts which parse the output of tarsnap -v, they may need to be updated. * tarsnap now prints a warning if you pass '--configfile /nosuchfile'. If you have scripts which rely on being able to specify nonexistent configuration files and not get any warnings from tarsnap, they may need to be updated. (Also, if you were doing that, I *really* want to know why.) There are also two changes which most users should not encounter: * tarsnap now has an --initialize-cachedir mode; this is intended for use by the GUI. (The cache directory will be initialized automatically in normal usage of the tarsnap command-line utility.) * tarsnap's configure script takes a --with-conf-no-sample option which results in the sample tarsnap configuration file being installed as "tarsnap.conf" rather than "tarsnap.conf.sample". This is intended for use in some packaging systems which have mechanisms for managing configuration files, and should probably not be used by hand (since it will overwrite your existing tarsnap.conf).
Update tarsnap to 1.0.37. First the new release: Tarsnap 1.0.37 is now available. This version brings the following substantive changes compared to tarsnap 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. As usual, there are also many minor build fixes, harmless bug fixes, and code refactoring / cleanup changes. For a full listing of changes, consult the tarsnap git repository: https://github.com/Tarsnap/tarsnap
Bump PKGREVISION for security/openssl ABI bump.
Pullup ticket #4797 - requested by wiz sysutils/tarsnap: security update Revisions pulled up: - sysutils/tarsnap/Makefile 1.10-1.11 - sysutils/tarsnap/distinfo 1.6-1.7 --- Module Name: pkgsrc Committed By: wiz Date: Fri Aug 21 14:43:17 UTC 2015 Modified Files: pkgsrc/sysutils/tarsnap: Makefile distinfo Log Message: Update to 1.0.36: 1. SECURITY FIX: When constructing paths of objects being archived, a buffer could overflow by one byte upon encountering 1024, 2048, 4096, etc. byte paths. Theoretically this could be exploited by an unprivileged user whose files are being archived; I do not believe it is exploitable in practice, but I am offering a $1000 bounty for the first person who can prove me wrong: http://www.daemonology.net/blog/2015-08-21-tarsnap-1000-exploit-bounty.html 2. SECURITY FIX: An attacker with a machine's write keys, or with read keys and control of the tarsnap service, could make tarsnap allocate a large amount of memory upon listing archives or reading an archive the attacker created; on 32-bit machines, tarsnap can be caused to crash under the aforementioned conditions. 3. BUG FIX: Tarsnap no longer crashes if its first DNS lookup fails. 4. BUG FIX: Tarsnap no longer exits with "Callbacks uninitialized" when running on a dual-stack network if the first IP stack it attempts fails to connect. 5. tarsnap now avoids opening devices nodes on linux if it is instructed to archive /dev/. This change may prevent "watchdog"-triggered reboots. 6. tarsnap -c --dry-run can now run without a keyfile, allowing users to predict how much Tarsnap will cost before signing up. 7. tarsnap now has bash completion scripts. 8. tarsnap now takes a --retry-forever option. 9. tarsnap now automatically detects and uses AESNI and SSE2. As usual, there are also many minor build fixes, harmless bug fixes, and code refactoring / cleanup changes. For a full listing of changes, consult the tarsnap git repository: https://github.com/Tarsnap/tarsnap --- Module Name: pkgsrc Committed By: wiz Date: Fri Aug 21 18:03:22 UTC 2015 Modified Files: pkgsrc/sysutils/tarsnap: Makefile distinfo Log Message: Update to 1.0.36.1: OS X lacks the POSIX-mandated clock_gettime function, and tarsnap is not using libcperciva's "support broken operating systems" compatibility mechanism yet. Add -DPOSIXFAIL_CLOCK_REALTIME to the build.
Update to 1.0.36.1: OS X lacks the POSIX-mandated clock_gettime function, and tarsnap is not using libcperciva's "support broken operating systems" compatibility mechanism yet. Add -DPOSIXFAIL_CLOCK_REALTIME to the build.
Update to 1.0.36: 1. SECURITY FIX: When constructing paths of objects being archived, a buffer could overflow by one byte upon encountering 1024, 2048, 4096, etc. byte paths. Theoretically this could be exploited by an unprivileged user whose files are being archived; I do not believe it is exploitable in practice, but I am offering a $1000 bounty for the first person who can prove me wrong: http://www.daemonology.net/blog/2015-08-21-tarsnap-1000-exploit-bounty.html 2. SECURITY FIX: An attacker with a machine's write keys, or with read keys and control of the tarsnap service, could make tarsnap allocate a large amount of memory upon listing archives or reading an archive the attacker created; on 32-bit machines, tarsnap can be caused to crash under the aforementioned conditions. 3. BUG FIX: Tarsnap no longer crashes if its first DNS lookup fails. 4. BUG FIX: Tarsnap no longer exits with "Callbacks uninitialized" when running on a dual-stack network if the first IP stack it attempts fails to connect. 5. tarsnap now avoids opening devices nodes on linux if it is instructed to archive /dev/. This change may prevent "watchdog"-triggered reboots. 6. tarsnap -c --dry-run can now run without a keyfile, allowing users to predict how much Tarsnap will cost before signing up. 7. tarsnap now has bash completion scripts. 8. tarsnap now takes a --retry-forever option. 9. tarsnap now automatically detects and uses AESNI and SSE2. As usual, there are also many minor build fixes, harmless bug fixes, and code refactoring / cleanup changes. For a full listing of changes, consult the tarsnap git repository: https://github.com/Tarsnap/tarsnap
Fix build on SunOS (needs explicit -lnsl).
Update to 1.0.35: Changes since version 1.0.34: A bug in tarsnap 1.0.34 which could cause tarsnap to crash (segmentation fault or bus error) when encountering network glitches or outages is fixed. When tarsnap encounters "insane" filesystems (procfs and other similar synthetic filesystems which are not reasonable to archive), it now archives the filesystem mount point but by default does not recurse into the filesystem. Previous releases (since 1.0.26) did not archive the synthetic filesystem mount point. Changes since version 1.0.33: Tarsnap now supports both IPv4 and IPv6. Tarsnap is now more resilient against short network glitches when it first connects to the Tarsnap server. Tarsnap now supports platforms with mandatory structure alignment (e.g., ARM OABI). Tarsnap now restores terminal settings if killed with ^C while reading a password or passphrase. Multiple minor bug fixes and cleanups.
Bulk build wants openssl
Needs zlib
Drop superfluous PKG_DESTDIR_SUPPORT, "user-destdir" is default these days.
Update tarsnap to version 1.0.33. Changes since version 1.0.32: - Tarsnap now caches archive metadata blocks in RAM, typically providing a 5x - 10x speedup and reduction in bandwidth usage in the "fsck" operation and when deleting a large number of archives at once. - Tarsnap's internal "chunk" metadata structure is now smaller, providing a ~10% reduction in usage on 32-bit machines and a ~30% reduction in memory usage on 64-bit machines. - Tarsnap's --newer* options now correctly descend into old directories in order to look for new files. (But note that tarsnap's snapshotting makes these options unnecessary in most situations.) - Multiple minor bug fixes and cleanups. Changes since version 1.0.31: - A bug affecting the handling of the --nodump option on Linux (and in most cases rendering it inoperative) is fixed. - A workaround has been added for a compiler bug in OS X 10.7 (Lion). - The NetBSD "kernfs" and "ptyfs" filesystems are now excluded from archival by default.
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.
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.
Follow Greg's advice and reimport in a better place, i.e. move tarsnap from security to sysutils.
Initial revision