linux-kernel - Re: [PATCH] led-class.c permission change

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: <20070506133759.650a6453@the-village.bc.nu>
Date:	Sun, 6 May 2007 13:37:59 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Colin Leroy <colin@...ino.net>
Cc:	Richard Purdie <rpurdie@...nedhand.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] led-class.c permission change

> > Take a look at the various pam console management modules (and also
> > beat people up to get revoke() support into the kernel).
> 
> So, you suggest me to link my plugin to libpam and find something that
> allows the plugin to write into /brightness? 

Much simpler than that. Most distributions have a pam module already
which updates permissions on things that the "console" user may want to
access directly (eg /dev/audio* /dev/cdrom etc) but which should
otherwise be protected from misuse (eg people with cronjobs that run
eject - an old an very funny SunOS prank)

If your distribution is like most and uses pam_console then see man 5
console.perms and add a rule to the /etc/security/console.perms file for
your file. At that point it will happily change the rights back and
forth for you as required.
-
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/