Thanks but that kind of lock is something I really dislike, doesn’t really make anything quicker or safer as you can always see where people have traced
I’m not sure to understand how it works. Do you need to replicate your normal security code on MazeLock 2.0? Like if your security code is 89650, you’ll need to use the same but on MazeLock 2.0?
The case against this idea is that it blurs the possibility of giving n attempts.
When an attacker progressively types “1234”, “12345”, “123456”, “1234567” and it’s not automatically unlocking, the attacker can rule out these codes without consuming an attempt, then press ⌫ or the power key (which clears the partial code) and try other codes.
To avoid brute force, the system has to automatically consume an attempt based on some criterion.
If it is when the definite number of alphanumerical characters is reached, then this leaks to the attacker the information of the number of characters used in the lock code.
Maybe it is “30 seconds timeout” or “used backspace”, but some users have good reasons to need time or use the backspace several times.
I guess “use of the power key” could be another criterion.
Personally I sometimes give up on typing the code because I realise all I need is the camera and I can have it from that screen. The possibility of using one of very few attempt puts me under a very small yet non-zero level stress and I don’t like stress.
So I think it’s great if proposed as an option but needs to be carefully thought with security in mind, and the user should be made aware of the potential security implications when activating this mode.
Yes its correct. You have to use your normal code and follow the numbers. Only ones is not possible. If you use double numbers like “25514” because its not possible to draw a line between 5-5. So you have to change it but please use the numeric keyboard for it. So you can see the numbers and wrote down it. I hope it works for you. You can test it without a lipstick restart in the root file browser
You say it´s also compatible with later versions (>5.0.0.67) but I think you have to set compatibility so one can install it in Patchmanager. Now it´s set to 5.0.0.67. *71 and *72 are not accepted. (“not compatible”)
Greetings and thx for this patch!
Oh, I just saw that one can deactivate version check. But then there´s a small danger that one bricks the phone. Hope small version number differences are no problem. Thx.
I may seem stupid but how is maze lock activated? I activated the patch, I can enter settings but when unlock screen shows the usual pin has to be entered. No maze lock field shows.
Well, I did that from within Patchmanager, I restarted gui from the Helper Scripts and tried a reboot with automatic start of the patches. No luck. By the way, I’m on a C2.
Srry for the late answer. Do you have restart the homescreen? The settigpage came without this but the keypad will changed first after restarting the homescreen. This works easy with the setting option from the patchmanager. This is normal at many patches. Good luck and sorry for the problems.
Yes, I played through all variants I know. Restarting services fron PM, restarting homescreen from helper scripts, and reboot with automated applying of the patch. But no maze lock.
But pleas don’t put yourself under pressure, no need to hurry! It’s great that someone is doing such things!