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-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8107d8a0e50b64dd45dc749da87b2c7b.squirrel@mungewell.org>
Date:	Fri, 16 Mar 2012 12:26:56 -0400
From:	simon@...gewell.org
To:	"John Stoffel" <john@...ffel.org>
Cc:	simon@...gewell.org, linux-input@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: Building BarGraph with LED subsystem


> 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.
>
> John
>

So what would be the best way to achieve this (once the code gets into
kernel)? I mean so that 'Jane Doe' get the LEDs working when she plugs in
her wheel...

At present the patch uses the devices ID's to register the LED's. ie.
--
Mar 14 14:57:35 ubuntu kernel: [ 6462.204185] Registered led device:
0003:046D:C294.0009::RPM1
Mar 14 14:57:35 ubuntu kernel: [ 6462.204251] Registered led device:
0003:046D:C294.0009::RPM2
Mar 14 14:57:35 ubuntu kernel: [ 6462.204301] Registered led device:
0003:046D:C294.0009::RPM3
Mar 14 14:57:35 ubuntu kernel: [ 6462.204354] Registered led device:
0003:046D:C294.0009::RPM4
Mar 14 14:57:35 ubuntu kernel: [ 6462.204402] Registered led device:
0003:046D:C294.0009::RPM5
--

Simon.


--
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