How to Install and Uninstall tar-split Package on Kali Linux
Last updated: November 22,2024
1. Install "tar-split" package
Learn how to install tar-split on Kali Linux
$
sudo apt update
Copied
$
sudo apt install
tar-split
Copied
2. Uninstall "tar-split" package
Please follow the steps below to uninstall tar-split on Kali Linux:
$
sudo apt remove
tar-split
Copied
$
sudo apt autoclean && sudo apt autoremove
Copied
3. Information about the tar-split package on Kali Linux
Package: tar-split
Source: golang-github-vbatts-tar-split (0.11.2+ds1-1)
Version: 0.11.2+ds1-1+b7
Installed-Size: 3798
Maintainer: Debian Go Packaging Team
Architecture: amd64
Depends: libc6 (>= 2.34)
Size: 1280344
SHA256: 61c7d1f70817fdf6b3a654065a66e6b56a975244056a9261a22b48da1516a52a
SHA1: 560e2231f4897614d7dc0a342e5dd3c63c6e722e
MD5sum: 30b997c64ec95c8a81a21ee562181249
Description: tar archive assembly/disassembly
Pristinely disassembling a tar archive, and stashing needed raw bytes and
offsets to reassemble a validating original archive.
.
Eventually this should detect TARs that this is not possible with.
.
For example stored sparse files that have "holes" in them, will be read as a
contiguous file, though the archive contents may be recorded in sparse format.
Therefore when adding the file payload to a reassembled tar, to achieve
identical output, the file payload would need be precisely re-sparsified. This
is not something I seek to fix immediately, but would rather have an alert that
precise reassembly is not possible. (see more
http://www.gnu.org/software/tar/manual/html_node/Sparse-Formats.html)
.
Other caveat, while tar archives support having multiple file entries for the
same path, we will not support this feature. If there are more than one entries
with the same path, expect an err (like ErrDuplicatePath) or a resulting tar
stream that does not validate your original checksum/signature.
Description-md5:
Homepage: https://github.com/vbatts/tar-split
Built-Using: go-md2man-v2 (= 2.0.2+ds1-1), golang-1.21 (= 1.21.3-1), golang-blackfriday-v2 (= 2.1.0-1), golang-github-urfave-cli (= 1.22.9-2), golang-golang-x-sys (= 0.12.0-1), golang-logrus (= 1.9.0-1)
Section: devel
Priority: optional
Filename: pool/main/g/golang-github-vbatts-tar-split/tar-split_0.11.2+ds1-1+b7_amd64.deb
Source: golang-github-vbatts-tar-split (0.11.2+ds1-1)
Version: 0.11.2+ds1-1+b7
Installed-Size: 3798
Maintainer: Debian Go Packaging Team
Architecture: amd64
Depends: libc6 (>= 2.34)
Size: 1280344
SHA256: 61c7d1f70817fdf6b3a654065a66e6b56a975244056a9261a22b48da1516a52a
SHA1: 560e2231f4897614d7dc0a342e5dd3c63c6e722e
MD5sum: 30b997c64ec95c8a81a21ee562181249
Description: tar archive assembly/disassembly
Pristinely disassembling a tar archive, and stashing needed raw bytes and
offsets to reassemble a validating original archive.
.
Eventually this should detect TARs that this is not possible with.
.
For example stored sparse files that have "holes" in them, will be read as a
contiguous file, though the archive contents may be recorded in sparse format.
Therefore when adding the file payload to a reassembled tar, to achieve
identical output, the file payload would need be precisely re-sparsified. This
is not something I seek to fix immediately, but would rather have an alert that
precise reassembly is not possible. (see more
http://www.gnu.org/software/tar/manual/html_node/Sparse-Formats.html)
.
Other caveat, while tar archives support having multiple file entries for the
same path, we will not support this feature. If there are more than one entries
with the same path, expect an err (like ErrDuplicatePath) or a resulting tar
stream that does not validate your original checksum/signature.
Description-md5:
Homepage: https://github.com/vbatts/tar-split
Built-Using: go-md2man-v2 (= 2.0.2+ds1-1), golang-1.21 (= 1.21.3-1), golang-blackfriday-v2 (= 2.1.0-1), golang-github-urfave-cli (= 1.22.9-2), golang-golang-x-sys (= 0.12.0-1), golang-logrus (= 1.9.0-1)
Section: devel
Priority: optional
Filename: pool/main/g/golang-github-vbatts-tar-split/tar-split_0.11.2+ds1-1+b7_amd64.deb