RHash Activity
Brought to you by:
aleksey14
Activity for RHash
-
dik kong created ticket #30
SUGGESTIONS
-
Aleksey modified ticket #50
Speed issue
-
The fix is included into RHash v1.4.6.
-
RHash released /rhash/1.4.6/README.md
-
-
-
-
-
-
-
-
The problem is fixed by commit edc311890. Fix will be included into RHash v1.4.6. Benchmarks: SHA1, 1.6GB file, Windows, Core i5 2.60GHz Speed Program 457 MBps rhash dev (with bugfix) 353 MBps sha1sum (hashutils) 249 MBps rhash v1.4.5 CRC32, 11GB file, Windows, Core i5 2.60GHz Speed Program 612 MBps rhash dev (with bugfix) 380 MBps crc32sum (hashutils) 364 MBps rhash v1.4.5 CRC32, 526MB file, Linux, Core i7 2.90GHz Speed Program 1974 MBps rhash dev (with bugfix) 1830 MBps rhash v1.4.5
-
How use "--printf=<format string>" from manual for RHash.exe? don't work!!!
-
The problem with case ignoring is that utf8 can represent many symbols with different codepoints. To corectly match such symbols the utility must depend on the heavyweight libicu library. That will complicate compilation and, probably, increase the utility start time. For more details read about CaseFolding. The ignore case feature implemented without libicu will be a source of future bugs, because for many languages it will incorectly match filenames with national characters. Due to shortage of...
-
-
-
-
-
-
-
-
-
v1.4.4 breaks Windows 2000/XP support
-
Fixed by commit a5f558af1b5e01922d5b9e2d2f56af5f2f2f07ff.
-
jax created ticket #29
Ignore filename case on file checking
-
Fishbulb created ticket #60
v1.4.4 breaks Windows 2000/XP support
-
-
-
-
-
-
-
-
-
bluemark posted a comment on ticket #59
Thank you.
-
1.4.3 directory - 3 files are missing
-
Fixed.
-
-
-
-
-
1.4.3 directory - 3 files are missing
-
-
-
-
-
-
-
raywood created ticket #58
Recursion Problem - VeraCrypt Drive
-
Thank you for the good work!
-
ripemd160 performance patches
-
After a long long time the first patch has been imported into the master branch: https://github.com/rhash/RHash/commit/3791df14de5b78eb54d71479f05dc300d902c839 Both the x86-64 and i686 tests on the Intel i7 CPU showed that the first patch is better.
-
-
-
-
-
-
-
-
-
-
-
LibRHash
-
Sergey Petrovich modified a comment on ticket #57
I figured out why double quotes don't work. I just used the Take Command program. Writing quotes in different programs works differently! In "cmd.exe" you can use double quotes: --printf="%f %{Md5}" In "Take Command" you need to wrap double quotes in single ones: --printf=`"%f %{Md5}" You can use double quotes in "JavaScript" : --printf=\"%f %{md5}\" https://i.ibb.co/DPFWMmW/rhash-cmd.png https://i.ibb.co/syB5dgz/rhash-Take-Command.png
-
I figured out why double quotes don't work. I just used the Take Command program. Writing quotes in different programs works differently! In "cmd.exe" you can use double quotes: --printf="%f %{Md5}" In "Take Command" you need to wrap double quotes in single ones: --printf=`"%f %{Md5}" You can use double quotes in "JavaScript" : --printf=\"%f %{md5}\"
-
I figured out why double quotes don't work. I just used the Take Command program. Writing quotes in different programs works differently! In "cmd.exe" you can use double quotes: --printf="%f %{Md5}" In "Take Command" you need to wrap double quotes in single ones: --printf="%f %{Md5}" You can use double quotes in "JavaScript" : --printf=\"%f %{md5}\"
-
I figured out why double quotes don't work. I just used the Take Command program. Writing quotes in different programs works differently! In "cmd.exe" you can use double quotes: --printf="%f %{Md5}" In "Take Command" you need to wrap double quotes in single ones: --printf="%f %{Md5}"` You can use double quotes in "JavaScript" : --printf=\"%f %{md5}\"
-
I figured out why double quotes don't work. I just used the Take Command program. Writing quotes in different programs works differently! In "cmd.exe" you can use double quotes: --printf="%f %{Md5}" In "Take Command" you need to wrap double quotes in single ones: --printf="%f %{Md5}" You can use double quotes in "JavaScript" : --printf=\"%f %{md5}\"
-
I figured out why double quotes don't work. I just used the Take Command program. Writing quotes in different programs works differently! In "cmd.exe" you can use double quotes: "D:\test\RHash-1.4.0-win64\rhash.exe" "D:\test\ExperienceIndexOK_x64_p.exe" --printf="%f %{Md5}" In "Take Command" you need to wrap double quotes in single ones: "D:\test\RHash-1.4.0-win64\rhash.exe" "D:\test\ExperienceIndexOK_x64_p.exe" --printf="%f %{Md5}" You can use double quotes in "JavaScript" : --printf=\"%f %{md5...
-
-
-
-
-
-
-
-
How use "--printf=<format string>" from manual for RHash.exe? don't work!!!
-
Allow to build against OpenSSl without MD4 support
-
Thanks for the patch! Applied as 551e07233.
-
Alexey Dokuchaev created ticket #7
Allow to build against OpenSSl without MD4 support
-
Add Blake3 and xxHASH
-
Closing this FR as duplicate of: 1. https://github.com/rhash/RHash/issues/52 2. https://github.com/rhash/RHash/issues/134 Note, that official Bug tracker is now at GitHub: https://github.com/rhash/RHash/issues
-
Francisco Laferrière created ticket #28
Add Blake3 and xxHASH
-
-
-
-
-
-
-
-
HashFunctions
-
HashFunctions
-
Interesting. I've run rhash --speed --ripemd160 against different CPUs on hot caches w/ lots of RAM: Intel E5500 @2803 MHz baseline: 159 MB/s patch #1: 190 MB/s patch #2: 191 MB/s AMD A8-5550M @1900 MHz (downclocked) baseline: 45.6 MB/s patch #1: 70.6 MB/s patch #2: 70.4 MB/s Intel i5-7200U @3113 MHz baseline: 314 MB/s patch #1: 332 MB/s patch #2: 332 MB/s
-
-
-
-
-
PublicKey
-
-
1 >
