[BUG] unlock with picture as keyfile no longer working on Samsung S23+

[marcelser]

Checks

• I have read the FAQ section, searched the open issues, and still think this is a new bug.

Describe the bug you encountered:

For years we've been using a 4MB picture to unlock our database. With latest release unlocking is no longer possible. K2A always reports that combined key is invalid. They keyfile is stored locally on a Samsung S23+. On windows unlocking with picture works perfectly fine. On Android with K2A it's broken.

Describe what you expected to happen:

Unlocking with our 4MB jpg file is working again. Currently we had to remove the keyfile by changing master key on windows to be able to use K2A.

What version of Keepass2Android are you using?

1.14-r4

Which version of Android are you on?

16

[VinVel]

Duplicate of #3211, #3225 and #1824. Maybe one of these will help you. TL;DR, change extension from .jpg to .jpg.key. It is not ideal but it works.

[marcelser]

Ok, I"ve read the other duplicate issues and it says it's present since Android 12 on pixel devices. But why does it happen all of a sudden on Android 16 on a Samsung S23+? And why is it only happening on the Samsung S23+? I also have a Samsung S24 FE also on latest Android 16 where it's working perfectly fine. And the security patches they received were 1 day apart which makes me believe they got the same fixes. Otoh the S23+ has 5.x kernel whereas the S24 FE runs on 6.x so even if it looks like they share the same Android 16 it might be quite different under the hood. So probably one cannot tell which devices will become affected and when although it still seems strange that Samsungs latest security fixes are really triggering this. My gutfeeling as a developer also tells me otherwise. I also really find it very hard to believe that there's no way to read a file in binary mode and getting altered data depending filetype. That sounds insane and could probably break lots of other apps too. I"m not convinced this cannot be fixed but I am not an Android developer and cannot really proof it otherwise. But think for example of apps that are copying files, it's impossible that they would create files that differ from the source just because it's a picture. But for the time beeing it seems we have to rename the keyfile. But I would really love to see a proper bugfix.

[Sean-T-Moore]

I was also affected by this. I had not updated android. Had not updated keepass2android either. Now can no longer use jpg file with .jpg extension as a keyfile. I tried another keepass app and got the same problem. Simply changing the extension from .jpg to .bin fixed it. Something about android not accepting a hash from a jpg file anymore, but it's a mystery as to why this started all of a sudden without me updating the system or the app.

[VinVel]

It is a mystery to all of us. Nobody knows exactly why this happens. For now, only this weird workaround is all we have.