![]() ![]() Even after fingerprint is locked out for 5 bad tries and the Master Password is then required, if I reboot the phone, I do NOT need to enter the Master password, i can use my fingerprint. SECURITY BUG: Rebooting the phone does not cause Enpass to require the Master Password to unlock the app. Again, literally just like you are doing it now with PIN quick unlock.ġ. ![]() Instead of all that, just have the app say when the fingerprint authentication is allowed. If I fail fingerprint authentication now, it doesn't delete my encrypted password, and I can just type the master password in with the keyboard (or I can force close the app or reboot the phone to try the fingerprint again). I don't see why this can't be done programmatically in your app. THAT'S ALL YOU HAVE TO DO to make Fingerprint quick-unlock a FAR FAR FAR FAR FAR more secure method than it is and put it on parity with PIN quick-unlock. After a failure of fingerprint authentication, force the input of the Master Password by keyboard, never allowing fingerprint authentication again UNTIL the Master Password has been correctly entered first. Force EVERY initialization of the app to require the Master Password by keyboard (just like you already do with the PIN quick unlock)Ģ. My entire point is not to blame Enpass for the inherent security risk of Fingerprint authentication (it's better than nothing and very convenient) but it's to blame Enpass for employing a worse level of security for the fingerprint quick unlock compared to the PIN quick unlock, IN THE SAME SOFTWARE.ġ. Future more, it's a concern for law enforcement which is legally able to make you unlock with your fingerprint. Surely you have to understand how ridiculous this is. They have unlimited tries, because ENPASS (as you are explaining to me) will NOT apply the same level of logic of security to the fingerprint (which is already less secure than the PIN) that they are already using for PIN quick unlock, namely, requiring Master Password on every initialization of the app and requiring Master Password after the failure of the fingerprint authentication (without some time our or reboot, or app close and restart to reset the ability to fingerprint authenticate). If someone gets me and my phone, and forces the use of my fingerprint, they can unlock my phone, and now they can get into my Enpass database. But ENPASS is making those risks far worse than they need to be, and far worse than they are simply with the other PIN approach, it's crazy. Of course, having fingerprint access is a user's choice and if they make that choice they need to know the risks involved. ![]() being forced to open the database with your fingerprint. an inconsistent methodology of security so users cannot expect the same level of security. ![]() My concern is not a brute force attack or someone trying to add a new fingerprint. There is no reason it should work EXACTLY the same way with the finger print. If you force close the app or reboot the phone, you don't get a chance to enter your PIN first, you MUST enter your Master Password. If the PIN is wrong EVEN ONCE, it forces you to use the Master Password. This is exactly what you do with the PIN method. ONLY AFTER that has happened, should Fingerprint support be available. ALWAYS ALWAYS ALWAYS require the typed Master Password for the initial load of the database (after the phone boots up, or after the app is opened from being force closed, whatever). On the other hand, if we delete the encrypted master password entirely on fingerprint authentication error (which sometimes happens with genuine users also for various reasons), it will lead to enable fingerprint support again from the Enpass settings and hence user inconvenience without any gain in Kumar I am certainly not one of your programmers, but from a logic point of view, it's very clear to me what the solution is. Even if someone knows your device code and tries to add a new fingerprint, Android will invalidate the Enpass fingerprint key immediately and master password will be asked next time. In other words brute-forcing by Fingerprint is almost impossible. Nobody can enter inside Enpass without your fingerprint. Unlocking by fingerprint is securely implemented in android OS and OS itself restricts a users after n number of bad tries. Firstly let me assure you this is not a security bug. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |