From: Stefan Schweizer <sschweizer@gmail.com>
To: linux-hotplug@vger.kernel.org
Subject: udev and cdrom permissions
Date: Wed, 10 Nov 2004 22:02:32 +0000 [thread overview]
Message-ID: <e796392204111014024814f58@mail.gmail.com> (raw)
Hi,
with udev we have the general problem that it sets the group disk for
every hd* device. With this normal users cant write or read cdroms
without being in the disk group which is a security problem.
We really need to assign the cdrom group to cdrom-devices.
I have 2 solutions to propose:
1) We make udev follow symlinks while setting permissions. So if udev
assigns permissions to /dev/cdroms/cdrom0 it should set the permission
for the source of the symlink.
2) We make hd* the symlink. This way /dev/cdroms/cdrom* and
/dev/discs/disc* would be the real device nodes and therefore have the
right permissions.
Do you have other possible solutions, and what solution doyou think is best?
Thanks
Stefan Schweizer
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_idU88&alloc_id\x12065&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next reply other threads:[~2004-11-10 22:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-10 22:02 Stefan Schweizer [this message]
2004-11-10 22:10 ` udev and cdrom permissions Marco d'Itri
2004-11-10 23:25 ` Stefan Schweizer
2004-11-11 18:52 ` Stefan Schweizer
2004-11-17 21:26 ` Stefan Schweizer
2004-12-02 22:26 ` Greg KH
2004-12-05 21:59 ` Stefan Schweizer
2004-12-06 23:03 ` Greg KH
2004-12-07 14:34 ` Kay Sievers
2004-12-07 17:51 ` Greg KH
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=e796392204111014024814f58@mail.gmail.com \
--to=sschweizer@gmail.com \
--cc=linux-hotplug@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 NNTP newsgroup(s).