All of lore.kernel.org
 help / color / mirror / Atom feed
* What changes my device permissions
@ 2010-06-08 10:20 Christoph Pleger
  2010-06-08 11:50 ` Michal Nazarewicz
  0 siblings, 1 reply; 3+ messages in thread
From: Christoph Pleger @ 2010-06-08 10:20 UTC (permalink / raw)
  To: linux-admin

Hello,

I have been using pam_devperm for a long time. If pam_devperm is
configured like I did, it causes that, when a user logs in on :0, the
permissions and ownerships of some device nodes in /dev are changed so
that the device file belongs to the user on :0 and has permissions
600. Now, I upgraded to a new OS version and found, that after logging
in on :0, some of the device file have permissions 660, not 600. It
seems that, after pam_devperm has changed the permissions to 600, some
other process resets them to 660.

How can I find out what is changing the device permissions?

Regards
  Christoph    

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: What changes my device permissions
  2010-06-08 10:20 What changes my device permissions Christoph Pleger
@ 2010-06-08 11:50 ` Michal Nazarewicz
  2010-06-08 14:42   ` Christoph Pleger
  0 siblings, 1 reply; 3+ messages in thread
From: Michal Nazarewicz @ 2010-06-08 11:50 UTC (permalink / raw)
  To: Christoph Pleger; +Cc: linux-admin

[-- Attachment #1: Type: text/plain, Size: 1256 bytes --]

Christoph Pleger <Christoph.Pleger@cs.tu-dortmund.de> writes:

> Hello,
>
> I have been using pam_devperm for a long time. If pam_devperm is
> configured like I did, it causes that, when a user logs in on :0, the
> permissions and ownerships of some device nodes in /dev are changed so
> that the device file belongs to the user on :0 and has permissions
> 600. Now, I upgraded to a new OS version and found, that after logging
> in on :0, some of the device file have permissions 660, not 600. It
> seems that, after pam_devperm has changed the permissions to 600, some
> other process resets them to 660.
>
> How can I find out what is changing the device permissions?

There's the hard way: use process accounting.

There's also easier way which *might* work: provide a shell wrapper for
chmod, like so:

$ : >/tmp/chmod-log && chmod 666 /tmp/chmod-log
$ cd /usr/bin
$ mv chmod chmod-
$ cat >chmod <<EOF
#!/bin/sh
echo "$@" >>/tmp/log
/usr/bin/chmod- "$@"
EOD

-- 
Best regards,                                         _     _
 .o. | Liege of Serenly Enlightened Majesty of      o' \,=./ `o
 ..o | Computer Science,  Michal "mina86" Nazarewicz   (o o)
 ooo +--<mina86-tlen.pl>--<jid:mina86-jabber.org>--ooO--(_)--Ooo--

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: What changes my device permissions
  2010-06-08 11:50 ` Michal Nazarewicz
@ 2010-06-08 14:42   ` Christoph Pleger
  0 siblings, 0 replies; 3+ messages in thread
From: Christoph Pleger @ 2010-06-08 14:42 UTC (permalink / raw)
  To: linux-admin

Hello,

On Tue, 08 Jun 2010 13:50:30 +0200
Michal Nazarewicz <mina86@tlen.pl> wrote:

> There's the hard way: use process accounting.
> 
> There's also easier way which *might* work: provide a shell wrapper
> for chmod, like so:

Unfortunately, these solutions did not help.

In the meanwhile, I found out that my original problem (wrong
permissions of devices, for example /dev/sr0) can be solved in two ways:

1. Deinstall consolekit
2. Use another display manager than gdm

But I am looking for a solution that works with every display manager,
and I need consolekit to solve other problems.

Regards
  Christoph 

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2010-06-08 14:42 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-06-08 10:20 What changes my device permissions Christoph Pleger
2010-06-08 11:50 ` Michal Nazarewicz
2010-06-08 14:42   ` Christoph Pleger

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.