From: Christoph Pleger <Christoph.Pleger@cs.tu-dortmund.de>
To: linux-admin@vger.kernel.org
Subject: What changes my device permissions
Date: Tue, 8 Jun 2010 12:20:37 +0200 [thread overview]
Message-ID: <20100608122037.175176ca.Christoph.Pleger@cs.tu-dortmund.de> (raw)
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
next reply other threads:[~2010-06-08 10:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-08 10:20 Christoph Pleger [this message]
2010-06-08 11:50 ` What changes my device permissions Michal Nazarewicz
2010-06-08 14:42 ` Christoph Pleger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100608122037.175176ca.Christoph.Pleger@cs.tu-dortmund.de \
--to=christoph.pleger@cs.tu-dortmund.de \
--cc=linux-admin@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).