Jacksum Activity
a free cross platform checksum utility, supports 58+ hash algorithms
Brought to you by:
jonelo
Activity for Jacksum
-
Antonio Ospite posted a comment on ticket #9
Thanks Johann, you know how they say: "good things come to those who wait". Ah, I just saw the release notes right after writing this :) Thanks again for jacksum Take care, Antonio
-
Johann N. Löfflmann posted a comment on discussion Open Discussion
Hi Devilus, hhhm, this must have been fallen through the cracks. Anyway thanks for your kind offer. Jacksum has moved to github meanwhile. See also See also https://github.com/jonelo/jacksum Jacksum 3 supports compatibility files in order to read and write foreign file formats. Feel free to file new feature requests on github, and thanks for your patience :-) Kind regards, Johann
-
Jacksum 3 supports Keccak with the bit width of 224, 256, 288, 384, and 512 , and of course all algos from the SHA-3 family, including SHAKE. Jacksum 3 is now on github. See also https://github.com/jonelo/jacksum
-
Hi Oleg, it has been a while, ... I have moved to github and I have just released Jacksum 3. See also https://github.com/jonelo/jacksum Release notes and download: https://github.com/jonelo/jacksum/releases/tag/v3.0.0 With respect to your request 1) the solution with Jacksum 3 is this: jacksum -s \n -a sha1+sha1+md5 -F "#ALGONAME{0}/hex: #CHECKSUM{0,hex} #FILENAME{NAME}#SEPARATOR#ALGONAME{1}/base32: #CHECKSUM{1,base32} #FILENAME{NAME} #SEPARATOR#ALGONAME{2}/base64: #CHECKSUM{2,base64} #FILENAME{NAME}#SEPARATOR"...
-
Kaiser posted a comment on ticket #21
There's also troubles when pointing Unicode-containing filenames in CLI, I found no workaround here
-
BOM support has been added to Jacksum 3. If a BOM is present in UTF-8 files it will be simply ignored.
-
Add BOM support
-
UTF-8 is necessary
-
I am pleased to announce that Jacksum 3 is on the web! See also https://github.com/jonelo/jacksum Download and release notes: https://github.com/jonelo/jacksum/releases/tag/v3.0.0 Jacksum 3 comes with charset support for both input and output and new options are available: --charset-check-file <charset> --charset-file-list <charset> --charset-error-file <charset> --charset-output-file <charset> which gives the maximum of flexibility for files. So from now on UTF-8 is the default if no charset has...
-
No more development?
-
Jacksum 3 is on the web. See also https://github.com/jonelo/jacksum/releases/tag/v3.0.0 Therefore I am closing this ticket. Could you please report new feature requests on github? Thanks, Johann
-
ArrayIndexOutOfBoundsException can occur during verification
-
closed, because Jacksum 3 doesn't support the metainfo creation anymore. Jacksum 3 and later supports compatibility files with regular expressions in order to parse check files that have been customized by the user. See also https://github.com/jonelo/jacksum/releases/tag/v3.0.0
-
fixed in Jacksum 3. See also https://github.com/jonelo/jacksum/releases/tag/v3.0.0 Thanks for your patience, Antonio. Cheers, Johann
-
Format option ignored when reading from stdin
-
Algorithms none+ and read+ return an unwanted checksum
-
fixed in Jacksum 3. See also https://github.com/jonelo/jacksum
-
Blake2b and SHA3 in the future?
-
I am pleased to announce that Jacksum 3 is on the web. See also https://github.com/jonelo/jacksum Jacksum 3 supports (among others): o SHA3-224, SHA3-256, SHA3-384, SHA3-512, SHAKE[128,256] o BLAKE-[224,256,348,512], o BLAKE2s-[8..256], o BLAKE2b-[8..512], and o BLAKE3 I am closing this issue. Since I have moved to github, could you please file new feature request on https://github.com/jonelo/jacksum/issues/new ? Thanks & have fun, Johann
-
Add Atkinson hash
-
closing, because I decided that Jacksum 3 and later shouldn't support password hash algorithms, those have limit constraints on the input and they cannot be used on files for example. BTW, I just released Jacksum 3 on https://github.com/jonelo/jacksum - feel free to file new feature requests on github :-)
-
Add BOM support
-
Sure thing! I'll open a request on BOM. Actually, we got different situations there. The issue with plain CMD is purely a matter of presentation (I suppose it has to do with font), but one can just copy/paste any Unicode output provided (using tools like RHash, eg). But in case of Jacksum, in CLI output it actually replaces unavailable chars with U+003f (question marks). I suppose there's a room for improvement.
-
Thanks! Workaround is very useful (maybe it would be great for incorporating it to FAQ). But CLI output (not file) continues to replace chars with '?'. Any way to fix that? I already know what BOM is. Some editors may be adding BOM sometimes, but it confuses the parser, unabling it to use hashlist file correctly. Read-only BOM support would be great, isn't it?
-
You're welcome! But CLI output (not file) continues to replace chars with '?'. Any way to fix that? AFAIK that is a limitation of the command prompt program. You could use the Window Terminal from Microsoft which comes with full UTF-8 character support. See also https://www.microsoft.com/store/productId/9N0DX20HK701 Once installed you can open the shell you want, and if you open the command prompt in Windows Terminal and change the code page to 65001 by typing chcp 65001 you should see all UTF-8...
-
Thanks! Workaround is very useful (maybe it would be great for incorporating it to FAQ). But CLI output (not file) continues to replace chars with '?'. Any way to fix that? I already know what BOM is. Some editors may be adding BOM sometimes, but it confuses the parses, unabling it to use hashlist file correctly. Read-only BOM support would be great, isn't it?
-
Thanks! Workaround is very useful (maybe it would be great for incorporating it to FAQ). But CLI output (not file) continues to replace chars with '?'. Any way to fix that?
-
missing fieldsep meta information if tab as separator has been used
-
duplicate of bug #6
-
Show progress option
-
I consider it for one of the next major releases.
-
UTF-8 is necessary
-
Workaround for Jacksum 1.7.0 in order to use UTF-8 for both input and output: java -Dfile.encoding=utf8 -jar jacksum.jar ... Some environments don't support UTF-8, so setting it as default could lead to unexpected behavior on those systems. The byte order has no meaning in UTF-8. The Unicode Standard permits the byte order mark (BOM) in UTF-8, but does not require or recommend its use. See also https://en.wikipedia.org/wiki/Byte_order_mark#UTF-8 Anyway, support for non-default charsets (including...
-
Ticket moved from /p/jacksum/support-requests/15/
-
UTF-8 is necessary
-
Absolutely. Stay tuned. For now please use the workarounds.
-
Show progress option
-
UTF-8 is necessary
-
Could we expect this issue to be fixed one day?
-
2nd workaround: append "fieldsep= ;" (without the quotes and a tab after the equals sign) to the 1st line of hashlist
-
missing fieldsep meta information if tab as separator has been used
-
missing meta information if tab as separator has been used
-
Incorrect formed list with using tab as separator
-
Ticket moved from /p/jacksum/support-requests/14/
-
Incorrect formed list with using tab as separator
-
I can reproduce the bug. Workaround is to ignore the meta information in hashlist and specifying the separator explicitly while checking: jacksum -I Jacksum -s \t -c hashlist
-
Incorrect formed list with using tab as separator
-
CRC64 - hash for file incorrect
-
Hi Sergey, thank you for your support request. Let's see ... Jacksum implements the crc64 that is defined in ISO 3309. See also Jacksum's manpage by entering: jacksum -h crc64 crc64 algorithm: CRC-64 ... comment: this algorithm is described in the ISO 3309 standard. (generator poly is x^64 + x^4 + x^3 + x + 1) Since Jacksum also supports the Rocksoft Model CRC Algorith model, you can verify it by passing the explicit parameters as defined in ISO 3309 for that model. Example: jacksum -a crc:64,1B,0,true,true,0...
-
Ticket moved from /p/jacksum/feature-requests/19/
-
Sergey Petrovich created ticket #19
CRC64 - hash for file incorrect
-
File Integration not working in Kubuntu 19.10
-
I have added support for the KDE Framework 5 to the Jacksum File Browser Integration on GNU/Linux. Please see the jacksum-1.7.0-linux-file-browser-integration-1.4.0.tar.bz2 in the files section on sourceforge.net.
-
Jacksum released /jacksum fbi/jacksum-1.7.0-linux-file-browser-integration-1.4.0.tar.bz2
-
Blake2b and SHA3 in the future?
-
The next major release of Jacksum will support (among others): o SHA3-224, SHA3-256, SHA3-384, SHA3-512, and o Blake2s and Blake2b (both with support for arbitrary output!) The implementation is done already on the algos above, please stay tuned. Kind regards, Johann
-
A. T created ticket #18
Blake2b and SHA3 in the future?
-
File Integration not working in Kubuntu 19.10
-
I can reproduce the issue also on Kubuntu 20.04. The root cause is that the KDE Framework 5 has changed the location of the config files (again) and therefore the current file browser integration cannot handle it, and you see all entries disabled. I am going to support the KDE Framework 5 so the file browser integration for Jacksum will work with Dolphin (and others) again. Please stay tuned.
-
Add Atkinson hash
-
hhmm, seems that some requests have been falling through the cracks. Thanks for submitting the feature request a few years ago :-) The implementation above has been released under the terms of the MPL (which is incompatible to the GPLv2+ and GPLv3+), but it has been released under the terms of the LGPL as well. So, I am considering it, but sureley not for the next release, because I don't want to further delay the next release. So please stay tuned, I won't forget any feature request. Kind regards,...
-
s-r-grass posted a comment on ticket #12
Please give me a link to which file to translate and attach it here, I will translate it into Russian!
-
No more development?
-
No more development?
-
Dear s-r-grass, many thanks for the link! Yes, there is still development. Actually I am working on the next major release which will come with some new algorithms (e.g. SHA3, Blake, Skein, etc.), new features, and improvements (e. g. multi processor/multi core support). It will still take some time to finish it, but I hope that it will be worth to wait for it. I am happy if you support the project with the translation into Russian for the upcoming release. большой привет, Johann
-
here is the link
-
No more development?
-
I just noticed everything is "DISABLED"
-
File Integration not working in Kubuntu 19.10
-
Format option ignored when reading from stdin
-
Thank you Antonio for the well prepared bug report. I can reproduce the issue, and I will fix it for the next release. Please stay tuned. Kind Regards, Johann
-
Format option ignored when reading from stdin
-
-
-
Rebecca G. Bettencourt created ticket #17
Add Atkinson hash
-
I would also find this option useful. I need to verify a ROM dump which is split...
-
PhoneixS posted a comment on ticket #15
Yes! Please release it into maven. It would be easier to add it to other projects....
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
1 >
