depmod -a and non-default umask

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello,

We've had a report[1] that depmod -a with a non-default umask (0027 in
this case) can leave the produced modules.* files with permissions other
than 0644.  Now, this isn't really a bug because depmod is already
explicit with its permissions and open/openat honor umask.  It can,
however, leave a machine in a state where non-root users can't read those
files.

I'm curious if people think depmod should set its own explicit umask to
ensure the file permissions are set to 0644.  If so, I could create a
patch to do this rather quickly.  I wanted to get the upstream opinion on
this situation first though.

Thanks,

josh

[1] https://bugzilla.redhat.com/show_bug.cgi?id=893037
--
To unsubscribe from this list: send the line "unsubscribe linux-modules" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux