Motion Sensor-based Privacy Attack on Smartphones · HackerPapers discussions

Motion Sensor-based Privacy Attack on Smartphones — mentioned by throwaway29303

Sun, 06 Nov 2022 02:10:45 GMT

They may not be eavesdropping with the microphone but they could be with an accelerometer[0]. In particular, we show that by exploiting the affected accelerometer readings and carefully selecting feature sets along with off-the-shelf machine learning techniques, Spearphone can perform gender classification (accuracy over 90%) and speaker identification (accuracy over 80%) for the audio/video playback on the smartphone for our recorded dataset. Google was capable of warning people of an earthquake before it even happened[1]. Google has also turned individual phones into miniature earthquake…

Paper and discussion history. A mention is not an endorsement.

Motion Sensor-based Privacy Attack on Smartphones — mentioned by wongarsu

Mon, 08 Nov 2021 14:44:49 GMT

So for context I looked at the papers behind the scenarios. - The heart rate sensing is done on a smart watch, not a phone, and needs data from the actual heart rate sensor every couple of days [1]. - The breathing rate is determined from a phone put on the breast or the abdomen [2]. Not really a threat vector in that form. - The audio stuff is incredibly impressive [3], but it doesn't look like they can reconstruct text with meaningful reliability, it's more about identifying the person or at least the gender of the person on the other end of the line. The location and activity detection…

Paper and discussion history. A mention is not an endorsement.

Motion Sensor-based Privacy Attack on Smartphones — HN submission

Mon, 08 Nov 2021 14:24:48 GMT

Motion Sensor-Based Privacy Attack on Smartphones

1 point; 0 discussion replies on HN. Paper and source history. A submission is not an endorsement.

Motion Sensor-based Privacy Attack on Smartphones — mentioned by tomasreimers

Tue, 22 Sep 2020 00:45:46 GMT

It's fascinating to me that gyroscope and accelerometer data don't seem to require permissions or explicit user opt-in on smartphones (at least that was true a few years ago and still seems true from a quick Google search, although I'm not sure if things have changed). As a side-channel, I've read about them being used for: - This. - Audio recordings of users (https://arxiv.org/pdf/1907.05972.pdf) - Keystrokes (https://medium.com/@tomasreimers/axolotl-a-keylogger-for-iph..., this one is shameless self-promotion and also why I'm interested in the topic) To me it seems that there are so few…

Paper and discussion history. A mention is not an endorsement.