-
Notifications
You must be signed in to change notification settings - Fork 138
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Invalid hash string, length does not match any known encoding" > Error Occurs. #99
Comments
Hi @soimkim There were 2 issues which required us to change some elements of TLSH
This caused changes to the generation of a few few files (edge cases) Which Java library of TLSH are you using? Cheers |
Hi @jonjoliver , I use the library (tlsh_3.7.1.jar) built in the java folder of this repository and call the "totalDiff, fromTlshStr" function that compares the tlsh value extracted from the tool as follows example.
I need a call from a spring based web service, so I need tlsh written in java. Thanks & regards, |
Just chasing down the developer who did the Java port Workaround: you could add a few lines of code to remove the T1 from the start of the hash that you get from Python |
Thank you very much for your quick reply! |
* Update TLSH Java implementation to understand new TLSH version data * Partial fix for issue #84 to allow TLSH on files up to 4GiB * Fix unit tests to work with new test data files * Remove bintray hosting as it is being shut down
@soimkim Could you test version 4.6.0 ? |
@jonjoliver , Thanks for responding quickly! |
This is an issue resolved in v4.6.0. |
When the hash value created with py_tlsh (4.5.0) is called with java, an "Invalid hash string, length does not match any known encoding" error occurs.
Would you reply to what should be corrected in the java code part to fix this error?
The text was updated successfully, but these errors were encountered: