Wrong hashes when characters outside of ISO 8859-1 are used about password4j HOT 7 CLOSED

Hi @GisoBartels thank you for providing a working example.

In the next days I will publish the fix for the issue. This might impact other projects but I think that very few people uses non-ASCII characters for their passwords.

from password4j.

Hi @GisoBartels 1.7.3 is released now!
Thank you for your support 🚀

from password4j.

Hi @GisoBartels,

can you provide a working example for this issue?
Thank you

from password4j.

Sure. I noticed the problem through a failing test in an update PR. See here: GisoBartels/kaster#8
The test went green again, when I compiled the latest version with UTF-8 as default charset.

from password4j.

From what I see the PR is failing because of a test about password generation not password hashing.

org.junit.ComparisonFailure: expected:<[g9*RlE3CilUmDL$#tyhX]> but was:<[PRqOXQNjODPVVuz6Ol5&]>
at org.junit.Assert.assertEquals(Assert.java:117)
at kotlin.test.junit.JUnitAsserter.assertEquals(JUnitSupport.kt:32)
at kotlin.test.AssertionsKt__AssertionsKt.assertEquals(Assertions.kt:63)
at kotlin.test.AssertionsKt.assertEquals(Unknown Source)
at kotlin.test.AssertionsKt__AssertionsKt.assertEquals$default(Assertions.kt:62)
at kotlin.test.AssertionsKt.assertEquals$default(Unknown Source)
at app.passwordkaster.core.PasswordGenerationTest.testPassword(PasswordGenerationTest.kt:110)

I don't see Password4j involved in that test. Please report here a piece of code where Password4j is involved, with input, output and expected output (from external tools if needed). I'm not going to analyze and debug third party libraries 😞

In 1.6.3 (and 1.7.x as well) we have a test with multi-byte unicodes and the test passed in all versions.
The string used was (っ＾▿＾)۶\uD83C\uDF78\uD83C\uDF1F\uD83C\uDF7A٩(˘◡˘ ) ❌❌ ❌❌❌. So it's weird that a backtick is breaking the hashing process.

Have you tried to convert strings to bytes with a different encoding? Password4j accepts also byte[] as well.
In java:

Password4j.hash("my password".getBytes(StandardCharsets.UTF_8)).with(...);

from password4j.

I created a test, so you can debug for yourself. The test will go green, when the default charset is set to UTF-8
#127

from password4j.

Thanks for fixing quickly 😊
I can confirm, that with the new version my tests are green again.

from password4j.