= 27d567bc2d48d9f40e9ccc20ea370b15)
Pentashagon comments on Open thread for December 17-23, 2013 - Less Wrong
You are viewing a comment permalink. View the original post to see all comments and the full post content.
= 783df68a0f980790206b9ea87794c5b6)
Loading…= b715d02e85f7b3b4ae65ca3d3e450868)
Subscribe to RSS Feed
Powered by Reddit
= f037147d6e6c911a85753b9abdedda8d)
You are viewing a comment permalink. View the original post to see all comments and the full post content.
Comments (301)
Eh... if an attacker has the level of physical access to the CPU that's required to plant a microphone, you have worse problems than acoustic attacks.
For personal devices the attacker may have access to the microphone inside the device via flash/java/javascript/an app, etc.
If the attacker can run code on your device, a keylogger is a much simpler solution.
I think it is probably simpler to enable the microphone from a web or mobile application than to install a keylogger in the OS. But then if you consider acoustic keyloggers...
With an acoustic keylogger you could scoop the my KeePass password but the actual passwords that I use to log into websites.
Not if it's sandboxed, but then timing and other side-channel attacks are still easier than using the mike.