Changeset e77b014 for postlfs

Timestamp:

08/25/2023 12:36:13 PM (10 months ago)

Author:

Xi Ruoyao <xry111@…>

Branches:

12.0, 12.1, ken/TL2024, ken/tuningfonts, lazarus, plabs/newcss, python3.11, rahul/power-profiles-daemon, renodr/vulkan-addition, trunk, xry111/llvm18

Children:

eb0031c

Parents:

78d568a

git-author:

Xi Ruoyao <xry111@…> (08/25/2023 12:29:00 PM)

git-committer:

Xi Ruoyao <xry111@…> (08/25/2023 12:36:13 PM)

Message:

Remove outdated text about usbfs

The usbfs psuedo file system has been removed since Linux 3.5.

File:

• postlfs/config/devices.xml (modified) (2 diffs)

postlfs/config/devices.xml

@@ -77 +77 @@
       successfully, the permissions have to be set correctly. By default, due
       to security concerns, all raw USB devices are owned by user root and
-      group usb, and have 0664 permissions (the read access is needed, e.g.,
+      group root, and have 0664 permissions (the read access is needed, e.g.,
       for lsusb to work and for programs to access USB hubs). Packages (such
       as SANE and libgphoto2) containing userspace USB device drivers also
@@ -88 +88 @@
 
     <para>
-      There is one situation when such fine-grained access control with
-      pre-generated udev rules doesn't work. Namely, PC emulators such as KVM,
-      QEMU and VirtualBox use raw USB device nodes to present arbitrary USB
-      devices to the guest operating system (note: patches are needed in order
-      to get this to work without the obsolete /proc/bus/usb mount point
-      described below). Obviously, maintainers of these packages cannot know
-      which USB devices are going to be connected to the guest operating
-      system. You can either write separate udev rules for all needed USB
-      devices yourself, or use the default catch-all "usb" group, members
-      of which can send arbitrary commands to all USB devices.
-    </para>
-
-    <para>
       Before Linux-2.6.15, raw USB device access was performed not with
       /dev/bus/usb/BBB/DDD device nodes, but with /proc/bus/usb/BBB/DDD
-      pseudofiles. Some applications (e.g., VMware Workstation) still use only
-      this deprecated technique and can't use the new device nodes. For them to
-      work, use the "usb" group, but remember that members will have
-      unrestricted access to all USB devices.  To create the fstab entry for
-      the obsolete usbfs filesystem:
-    </para>
-
-<screen><literal>usbfs  /proc/bus/usb  usbfs  devgid=14,devmode=0660  0  0</literal></screen>
-
-    <note>
-      <para>
-        Adding users to the "usb" group is inherently insecure, as they can
-        bypass access restrictions imposed through the driver-specific USB
-        device nodes. For instance, they can read sensitive data from USB
-        hard drives without being in the "disk" group. Avoid adding users
-        to this group, if you can.
-    </para>
-    </note>
+      pseudofiles. Some applications still use only
+      this deprecated technique and can't use the new device nodes.  They
+      cannot work with Linux kernel version 3.5 or newer.  If you need to
+      run such an application, contact the developer of it for a fix.
+    </para>
 
   </sect2>