Re: About IR Receivers and security
Bengt Martensson <[email protected]>
| Newsgroups | gmane.comp.hardware.lirc |
|---|---|
| Message-ID | <[email protected]> |
On 10/13/17 14:56, Egoitz Aurrekoetxea wrote: > >>> "Can you suffer a security issue having the IR Receiver operative >>> although without configuring any kind of user space daemon? At least... >>> not conscientiously.... >> >> Well, if you consider an arbitrary input device a problem, yes. The >> kernel provides decoding of many ir remotes out of the box and without >> any userspace code. Just a few comments: A certain degree of "paranoia" is likely a good thing here. Although the danger associated with sniffing IR commands is probably quite low in comparison with other IoT related problems... I think the completely open socket interface to lircd is a much worse problem, something an attacker can use to cause, at least, a considerable amount of annoyance. (Implementing TV-B-Gone for lircd https://en.wikipedia.org/wiki/TV-B-Gone ?) I wrote this down as a lirc ticket https://sourceforge.net/p/lirc/tickets/312/ . > Put a piece of tape over the IR receiver - problem solved (just as > some Facebook inventor uses tape over his laptop camera). What is transparent for visual light is not necessary transparent for IR, and vice versa. I would not trust "a piece of tape"; better to use something thicker... Greetz, Bengt ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot