Skip to content

v3.0.1

Choose a tag to compare

View all tags
@jonelo jonelo released this 03 Oct 22:45
· 545 commits to main since this release
v3.0.1
7d75077

  • added minor features

    • added algorithm aliases crc32_jamcrc and crc-32_jamcrc for crc32_ubi
    • added algo aliases sha512t224, sha512t256, skein256, skein512, and skein1024
    • added compat aliases called linux-tagged and linux-untagged (for bsd and linux)
    • added compat files called solaris-tagged and solaris-untagged
    • added format aliases #ALGONAME{lowercase} and #ALGONAME{<i>,lowercase}

  • improved build-in help

    • 'jacksum -h parameters', 'jacksum -h options', and 'jacksum -h algorithms'
      show the corresponding section entirely
    • fixed: jacksum -h examples shows only the first 3 example sections, it should show all example sections
    • added info to the manpage about "cksum -a " which exists starting with the GNU Core Utilities 9.0
    • added KeccakSum compatibility info to the help file
    • fixed some typos in the help file

  • bugs fixed

    • fixed: regression: files that have been specified by -o,-O and -u,-U are hashed, but they shouldn't
    • fixed: if both errorFile and outputFile are set to the same file, their paths must be normalized before comparisons
    • fixed: a NPE is thrown if a non-compatibility file is given by option -C
    • fixed: the syntax version of the compatibility files should be checked before processing
    • fixed: compat files bsd, linux, and openssl should use line separator \n on Microsoft Windows,
      otherwise md5sum, sha1sum, etc. on GNU/Linux cannot read Jacksum's output
    • fixed: typo in compat files linux and openssl which results in wrong stdin names
    • fixed: Jacksum does not print 100% compatible output by using tagged compat files (bsd, and openssl)
    • fixed: Jacksum does not parse 100% compatible output by using tagged compat files (bsd, and openssl)
    • fixed: speed rank info is calculated wrongly (check with jacksum -a all --list --info)
    • fixed: formats #HASH{0,<encoding>} and #CHECKSUM{i,<encoding>} don't work if the user has selected one algorithm only
    • fixed: crc32c can be used normal, but it is missing in the --list output
    • fixed: remove the lab-remnant hex-camelcase from the code
    • fixed: a potential mem leak in the Blake3 implementation
    • fixed: don't print a warning about implicitly set format if we have set -C and we are in check mode

reliable hash values of jacksum-3.0.1.jar (also included in jacksum-3.0.1-executable.zip):

SHA256:               88949a34a0f1302e776c8d70937bb8bb2a856178bb1691ef75aff24bc4eac06b
SHA3-256:             5f73ec467fb0cda351057835de10b26515f326d0807687663d61a78bc9aa0a3d
SHAKE128:             57d6b49686006ab0ee7ed78693bc9cd77d49da8c914e4d3adc62eef6d42d394e
BLAKE3:               122a50f45da98abfbbb9ff15502a536f1e08cc230f6bef6e9d7e550fa53bbc89
BLAKE2b-512 (base64): NDqIGkuPxLqpTQRH5mi8SLcWU6QChPZj3boXPHT2BE76l2JLI6N/qFg1XQLILGiz8C536L+cFIB1N/VnBq+ltA==
SHA3-512 (base64):    c6xLEDw4x6ii69yxLcjZkN27gWBUDWBcvlodhILbjxWqe1l9SxYhgsd+xbXD73r18ZAZNJleJd59hq4eMwuKRw==
SHAKE256 (base64):    spCQ2HBeD5gZNNYLgd304QagZAfrnZdnVSg85yquzWSelzqnoVWTkTY8MwrNVr5CXOfNy0xHL0uhihJdx0x9HQ==
Assets 6
Loading