Alexander Bakker 8c658ac930 Use the old encode method for passwords over 64 bytes and repair the slot (#98) ... Commit afb9e59711 fixed a bug where the password encode function would add null bytes to the end of the output. Luckily (I thought), PBKDF2 produces collisions for inputs with trailing null bytes and thus scrypt does this as well, so we could safely change that function to remove the null bytes without any impact. Unfortunately, that doesn't hold up if the password is over 64 bytes in size. So after that change, the KDF started producing different keys than before for such passwords and thus some users could no longer unlock their vault. This patch addresses the issue by using the old password encode function for passwords over 64 bytes and repairing the affected password slot.		2019-05-26 23:52:20 +02:00
..
src	Use the old encode method for passwords over 64 bytes and repair the slot (#98)	2019-05-26 23:52:20 +02:00
.gitignore	Initial commit	2016-08-15 21:29:41 +02:00
build.gradle	Release v0.4.1	2019-05-22 00:19:32 +02:00
proguard-rules.pro	Initial commit	2016-08-15 21:29:41 +02:00