Editing Talk:1808: Hacking
Please sign your posts with ~~~~ |
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 31: | Line 31: | ||
:::By hardware for audio input I meant electronic circuits inside the sound card that accept analog input and convert it to a digital signal. If a device is designed just for sound output it might not have the necessary electronics for sound input. --[[Special:Contributions/162.158.92.34|162.158.92.34]] 21:52, 9 March 2017 (UTC) | :::By hardware for audio input I meant electronic circuits inside the sound card that accept analog input and convert it to a digital signal. If a device is designed just for sound output it might not have the necessary electronics for sound input. --[[Special:Contributions/162.158.92.34|162.158.92.34]] 21:52, 9 March 2017 (UTC) | ||
β | :If the device uses a RealTek ( | + | :If the device uses a RealTek (and maybe others) audio codec chip, malware may silently "retask" the output channel as an input channel and record sound from normally connected speakers [https://www.wired.com/2016/11/great-now-even-headphones-can-spy/ without any hardware modification]. --[[Special:Contributions/162.158.92.34|162.158.92.34]] 15:16, 9 March 2017 (UTC) |
If the gcc/bash thing was actually a reference to ShellShock or some other real problem, then its inclusion wouldn't be funny... [[Special:Contributions/162.158.74.51|162.158.74.51]] 19:18, 8 March 2017 (UTC) | If the gcc/bash thing was actually a reference to ShellShock or some other real problem, then its inclusion wouldn't be funny... [[Special:Contributions/162.158.74.51|162.158.74.51]] 19:18, 8 March 2017 (UTC) |