![]() |
Test device lock
1 Attachment(s)
Hi,
Due I forgot device lock number I figured how you can ask on correct device lock or reset it. For this purpose is there app /usr/lib/qt5/plugins/devicelock/encpartition Arguments: Code:
--is-set lockcode else as standard output. Configuration is stored at directory /usr/share/lipstick/devicelock/ and encrypted/hash key is stored at /usr/share/lipstick/devicelock/.devicelock.enc, quite interesting are stored texts at binary file encpartition: 41414141, 42424241, 123456789012345 and /dev/block/platform/msm_sdcc.1/by-name/QOTP . More on http://www.onlinedisassembler.com/odaweb/4fDoTf/0 Unfortunately still don't know how reset device lock without sending to repair facility or brute-force. Test all numbers with length 5 takes less than 3 hours on the phone with utilizing 20% of CPU. |
Re: Test device lock
Quote:
|
Re: Test device lock
Thanks for the bugreport. I'll have to implement slowdown between attempts to make brute force slower.
It's recomended to have 8-10 digit lockcode to make developer mode bruteforcing to take months untill fix arrives. In the future we would appriciate that if you find weakness in system that you would contact security@jolla.com before posting it publically, so we would have time make a fix for it. |
Re: Test device lock
Quote:
Code:
[CLEANUP] Starting cleanup! |
Re: Test device lock
--imei hmmm sounds interresting ......
|
Re: Test device lock
Quote:
|
Re: Test device lock
Quote:
|
Re: Test device lock
Quote:
|
Re: Test device lock
Quote:
|
Re: Test device lock
Quote:
edit: however interesting concept and actual anti-theft measure this looks like not really implementable, problems with identifying the real owner will get only bigger once second hand market revves up |
All times are GMT. The time now is 01:02. |
vBulletin® Version 3.8.8