Re: Bug#342455: tech-ctte: Ownership and permissions of device mapper block devices
-----BEGIN PGP SIGNED MESSAGE-----
Bastian Blank <firstname.lastname@example.org> writes:
> On Fri, Dec 16, 2005 at 02:43:29PM -0500, Raul Miller wrote:
>> On 12/16/05, Bastian Blank <email@example.com> wrote:
>> > On Wed, Dec 14, 2005 at 01:54:45PM +0000, Ian Jackson wrote:
>> > > Are you saying that the current default permissions on (eg) /dev/hda*
>> > > are insecure and therefore wrong ?
>> > Yes, I overwrite them on my machines.
>> And what is your reason for being unwilling to use the same procedure
>> on devmapper disks?
> Which procedure? You seem to know something I don't know. ("Overwrite"
> means in my context: chmod of static devices or a MODE setting in the
> udev config)
A chown/chmod of the device is not scalable or practical. If I create
a new LV, the permissions will be wrong. If I run vgchange, the
permissions will be wrong. This is not a solution.
What if the user isn't using udev?
Do you have any example udev rules to do what you suggest?
Since udev, by default, does not get involved with creation of any
device mapper device other than /dev/mapper/control, the default
ownership and permissions come directly from the devmapper configure.
This is what needs fixing first. I would, however, like to see udev
become involved to allow this sort of customisation, but you will need
to work out the details with Marco d'Itri, the udev maintainer.
Printing on GNU/Linux? http://gimp-print.sourceforge.net/
Debian GNU/Linux http://www.debian.org/
GPG Public Key: 0x25BFB848. Please sign and encrypt your mail.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8+ <http://mailcrypt.sourceforge.net/>
-----END PGP SIGNATURE-----