[ConsoleKit] Permissions with consolekit and gdm
brian.cameron at oracle.com
Fri Jul 2 10:26:03 PDT 2010
Note that you could try changing the device permissions in the GDM
PreSession/PostSession scripts instead. If, for some reason, there is
a problem changing permissions from within PAM modules, then these GDM
hooks are another interface you could try. How to use this is in the
GDM manual in the Configuration section.
If you are running on OpenSolaris, the odd behavior you might be seeing
might be how logindevperm(4) works. If you are using a different OS
that is not Linux, then they also may have their own solution since not
all distros support udev. There could be a conflict between your
mechanism and the system one. If the system already supports an
interface to manage this (such as logindevperm), then you may not need
to use a PAM module.
Odd behavior also could be due to the fact that the PAM code was very
much redesigned in the rewritten GDM (2.21 and later) and all the bugs
may not be shaken out yet. So odd behavior could be a bug in GDM or
ConsoleKit or elsewhere.
On 07/ 2/10 01:45 AM, Christoph Pleger wrote:
> I have been using pam_devperm.so for a long time. pam_devperm.so is a
> PAM module that, with my configuration, changes the ownerships and
> permissions of some device nodes in /dev when a user logs in on :0, so
> that the device nodes belong to that user and get permissions 600.
> Now I realized that if consolekit is installed and additionally gdm is
> used as display manager, the permissions of the device nodes are set to
> 600, but then they are reset to 660.
> What does consolekit do that causes the permissions to be changed if
> gdm is used as display manager?
> ConsoleKit mailing list
> ConsoleKit at lists.freedesktop.org
More information about the ConsoleKit