Summary: | sys-fs/udev-140: no rule for raw1394 device | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Cyril <cyril.baletaud> |
Component: | [OLD] Library | Assignee: | udev maintainers <udev-bugs> |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | CC: | stefan-r-bz |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Cyril
2009-03-20 20:29:48 UTC
Upstream removed that group assignment for security reasons: See http://git.kernel.org/?p=linux/hotplug/udev.git;a=commit;h=a8cf7cf2c7b4c41c14508a808b09a5fa9256a024 for the upstream change. More links about that topic: * https://bugs.launchpad.net/ubuntu/+source/kino/+bug/6290/comments/21 * http://thread.gmane.org/gmane.linux.kernel.firewire.devel/6395/focus=6395 * http://article.gmane.org/gmane.linux.hotplug.devel/13531/match=raw1394 Upstream did not remove it for security reasons, they removed it because Ubuntu did it. The udev maintainers did not consult the maintainers of the IEEE 1394 kernel drivers and libraw1394 when they did this. And the Ubuntu maintainers removed it because they have a limited understanding of IEEE 1394 security concerns. As the consequence, IEEE 1394 is not working on Ubuntu without manipulation of system files by end users. (Except for storage = SBP-2 and IP-over-1394, which don't require userspace access to the 1394 bus.) Here is my comment on the upstream udev change (when I noticed it, months after it was committed), and Kay Siever's response: http://thread.gmane.org/gmane.linux.hotplug.devel/13969 Kernel 2.6.37 (January 2011) and newer does not contain raw1394 anymore. Perhaps this bug can therefore be closed as won't-fix. Users of ra1394 on older kernels will still be affected but can at least work around it by adding an own rule (once they figured out that they need it). Closing as per Comment #3 |