linux-kernel - Re: sysfs permitions on class leds

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] [day] [month] [year] [list]

Message-ID: <20070527024556.GA8405@kroah.com>
Date:	Sat, 26 May 2007 19:45:56 -0700
From:	Greg KH <greg@...ah.com>
To:	Rodrigo Pereira <rodripe@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: sysfs permitions on class leds

On Fri, May 25, 2007 at 03:37:46PM -0300, Rodrigo Pereira wrote:
>  (sorry my English)
> 
>  I'm helping M?rton N?meth  in a experimental mail led driver
>  leds-clevo-mail.c for clevo laptops and I have problems with this
>  driver:
>  this files
>  /sys/class/<ledname>trigger,  /sys/class/<ledname>/dalay_on and
>  /sys/class/<ledname>/delay_off  are  created  as 644 permissions. Also
>  ROOT controls the led. I think write udev rules but my rules don't
>  change this permissions.
> 
>  The clevo mail led is a trigger led (time-trigger) for blinks the led
>  when a new mail arrives.
> 
>  How can I change the permissions of the sysfs objects in runtime or 
>  userspace?

Just do a 'chmod' on the sysfs file.  If you have the proper permissions
to do that, it will stick for as long as the sysfs file stays around.

hope this helps,

greg k-h
-
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/