Guessing smart phone PINs by monitoring the accelerometer
1–10 of 72 posts
Re: Guessing smart phone PINs by monitoring the accelerometer
#2Re: Guessing smart phone PINs by monitoring the accelerometer
#3I guess I’m not blaming anyone here, just amazed that there isn’t any data source that doesn’t leak something sensitive!
Re: Guessing smart phone PINs by monitoring the accelerometer
#4Re: Guessing smart phone PINs by monitoring the accelerometer
#5The original intent is to make it much harder for onlookers to guess your pin based on finger movements. This could however apply equally well to the usecase of the article.
It is a bit of a usability trade-off though as you can't enter a pin using muscle memory alone anymore, as you must first understand the current keypad layout.
Re: Guessing smart phone PINs by monitoring the accelerometer
#6I suspect issues like this are one of the reasons why iOS locked down accelerometer access in Safari. Motion sensors have a lot more potential for malicious use than most users think.
Re: Guessing smart phone PINs by monitoring the accelerometer
#7Re: Guessing smart phone PINs by monitoring the accelerometer
#8I came across an interesting solution to this while paying at a restaurant in Ecuador: they used an Android device which randomized the position of the numbers of the on-screen keypad before each transaction. The original intent is to make it much harder for onlookers to guess your pin based on finger movements. This could however apply equally well to the usecase of the article. It is a bit of a usability trade-off…
Re: Guessing smart phone PINs by monitoring the accelerometer
#9Re: Guessing smart phone PINs by monitoring the accelerometer
#10I came across an interesting solution to this while paying at a restaurant in Ecuador: they used an Android device which randomized the position of the numbers of the on-screen keypad before each transaction. The original intent is to make it much harder for onlookers to guess your pin based on finger movements. This could however apply equally well to the usecase of the article. It is a bit of a usability trade-off…