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
| ||
|
Date: Fri, 16 Mar 2012 12:57:18 -0400 From: "John Stoffel" <john@...ffel.org> To: simon@...gewell.org Cc: "John Stoffel" <john@...ffel.org>, linux-input@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: Building BarGraph with LED subsystem >>>>> "simon" == simon <simon@...gewell.org> writes: simon> Also I have a question about the default permissions on the LED simon> controls; Is it possible to register LEDs so that users have simon> write permission? At present the controls are only accessible simon> as root. >> >> udev is the answer here. You probably want to make it so that the >> LEDs are open to the user logged into the system console or currently >> active Xsession. simon> So what would be the best way to achieve this (once the code simon> gets into kernel)? I mean so that 'Jane Doe' get the LEDs simon> working when she plugs in her wheel... Well, if you have an application that wants to control the wheel LEDs, then it needs to plug in an discover whether the wheel exists, whether it's got LEDs, etc. All part of the HID subsystem as understand it. simon> At present the patch uses the devices ID's to register the LED's. ie. simon> -- simon> Mar 14 14:57:35 ubuntu kernel: [ 6462.204185] Registered led device: simon> 0003:046D:C294.0009::RPM1 simon> Mar 14 14:57:35 ubuntu kernel: [ 6462.204251] Registered led device: simon> 0003:046D:C294.0009::RPM2 simon> Mar 14 14:57:35 ubuntu kernel: [ 6462.204301] Registered led device: simon> 0003:046D:C294.0009::RPM3 simon> Mar 14 14:57:35 ubuntu kernel: [ 6462.204354] Registered led device: simon> 0003:046D:C294.0009::RPM4 simon> Mar 14 14:57:35 ubuntu kernel: [ 6462.204402] Registered led device: simon> 0003:046D:C294.0009::RPM5 simon> -- This part is probably fine, but I'd call it 'LED1..5' instead, since they're LEDs, not true RPM indicators. I guess what I'm trying to say is that putting as much of this into user space, makes for a much more flexible environment. You might want to look into the Linux HID sub-system for how it enumerates the abilities of devices like keyboards, game pads, etc. They already have alot of that infrastructure in place. John -- 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