lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1384362765.13620.47030097.09D237AE@webmail.messagingengine.com>
Date:	Wed, 13 Nov 2013 09:12:45 -0800
From:	randmedia@...mail.org
To:	Jim Bos <jim876@...all.nl>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: How to correctly disable LIRC-related MCE*/IR_* modules,
 to remove ID of RemoteControl as BOTH keyboard & remote?

Hi Jim,

On Wed, Nov 13, 2013, at 08:52 AM, Jim Bos wrote:
> Have you looked at this sysfs-file, specifically tried this:
> 
> echo lirc > /sys/class/rc/rc0/protocols

In short, yes.

atm, I've this udev rule,

	cat /etc/udev/rules.d/70-infrared.rules
		ACTION=="add", SUBSYSTEM=="rc",
		RUN+="/usr/bin/ir-keytable --clear --protocol=LIRC
		--write=/etc/rc_keymaps/my_streamzap_rpi"

which ensures after boot

	ir-keytable
	Found /sys/class/rc/rc0/ (/dev/input/event2) with:
	        Driver streamzap, table rc-streamzap
	        Supported protocols: LIRC 
	        Enabled protocols: LIRC 
	        Repeat delay = 500 ms, repeat period = 125 ms

which correlates to

	cat  /sys/class/rc/rc0/protocols 
		[lirc]

i.e., the same effect as the manual intervetion of

	echo lirc > /sys/class/rc/rc0/protocols

nonetheless, that _alone_, does NOT 'do the trick'.  if those MCE*
kernel mods are around, i.e., if I have NOT disabled them in the kernel
(re)compile, or, similarly, use the distro-provided kernel which
compiles the mods by default, then -- at boot -- the Streamzap is
recognized/assigned as an MCE keyboard/remote.

rand
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ