[New: openFATE 308360] use lockdev
Feature added by: Ludwig Nussel (lnussel) Feature #308360, revision 1 Title: use lockdev openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: Ludwig Nussel (lnussel) Description: Ever since resmgr was dropped there is no way for unprivileged users to lock a device file such as /dev/ttyS0 even if the user has access to the device. A similar problem exists for usb devices in /dev/bus/usb. RedHat uses lockdev to solve the problem. It's a setgid 'lock' binary that manages the lock files. /var/lock is writeable by group 'lock' only. To be really useful the lockdev code needs to be cleaned up so a library is used to call the 'lockdev' helper binary. That way rpm would automatically catch the dependency. Any program accessing serial ports or usb devices as user could make use of lockdev, e.g. libgphoto2 minicom ppp sane-backends screen uucp ... References: http://cvs.fedoraproject.org/viewvc/devel/lockdev/ http://packages.debian.org/unstable/source/lockdev http://www.pathname.com/fhs/pub/fhs-2.3.html#VARLOCKLOCKFILES -- openSUSE Feature: https://features.opensuse.org/308360
Feature changed by: Ludwig Nussel (lnussel) Feature #308360, revision 2 Title: use lockdev openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: Ludwig Nussel (lnussel) Description: Ever since resmgr was dropped there is no way for unprivileged users to lock a device file such as /dev/ttyS0 even if the user has access to the device. A similar problem exists for usb devices in /dev/bus/usb. RedHat uses lockdev to solve the problem. It's a setgid 'lock' binary that manages the lock files. /var/lock is writeable by group 'lock' only. To be really useful the lockdev code needs to be cleaned up so a library is used to call the 'lockdev' helper binary. That way rpm would - automatically catch the dependency. Any program accessing serial ports - or usb devices as user could make use of lockdev, e.g. libgphoto2 - minicom ppp sane-backends screen uucp ... References: - http://cvs.fedoraproject.org/viewvc/devel/lockdev/ http://packages.debian.org/unstable/source/lockdev + automatically catch the dependency. + Any program accessing serial ports or usb devices as user could make + use of lockdev, e.g. + * libgphoto2 + * minicom + * ppp + * sane-backends + * screen + * uucp + * ... + References: + http://cvs.fedoraproject.org/viewvc/devel/lockdev + http://packages.debian.org/unstable/source/lockdev http://www.pathname.com/fhs/pub/fhs-2.3.html#VARLOCKLOCKFILES -- openSUSE Feature: https://features.opensuse.org/308360
Feature changed by: Ludwig Nussel (lnussel) Feature #308360, revision 5 Title: use lockdev - openSUSE-11.3: Unconfirmed + openSUSE-11.3: Done Priority Requester: Important Requested by: Ludwig Nussel (lnussel) Partner organization: openSUSE.org Description: Ever since resmgr was dropped there is no way for unprivileged users to lock a device file such as /dev/ttyS0 even if the user has access to the device. A similar problem exists for usb devices in /dev/bus/usb. RedHat uses lockdev to solve the problem. It's a setgid 'lock' binary that manages the lock files. /var/lock is writeable by group 'lock' only. To be really useful the lockdev code needs to be cleaned up so a library is used to call the 'lockdev' helper binary. That way rpm would automatically catch the dependency. Any program accessing serial ports or usb devices as user could make use of lockdev, e.g. * libgphoto2 * minicom * ppp * sane-backends * screen * uucp * ... References: http://cvs.fedoraproject.org/viewvc/devel/lockdev http://packages.debian.org/unstable/source/lockdev http://www.pathname.com/fhs/pub/fhs-2.3.html#VARLOCKLOCKFILES -- openSUSE Feature: https://features.opensuse.org/308360
Feature changed by: Monte Milanuk (memilanuk) Feature #308360, revision 6 Title: use lockdev openSUSE-11.3: Done Priority Requester: Important Requested by: Ludwig Nussel (lnussel) Partner organization: openSUSE.org Description: Ever since resmgr was dropped there is no way for unprivileged users to lock a device file such as /dev/ttyS0 even if the user has access to the device. A similar problem exists for usb devices in /dev/bus/usb. RedHat uses lockdev to solve the problem. It's a setgid 'lock' binary that manages the lock files. /var/lock is writeable by group 'lock' only. To be really useful the lockdev code needs to be cleaned up so a library is used to call the 'lockdev' helper binary. That way rpm would automatically catch the dependency. Any program accessing serial ports or usb devices as user could make use of lockdev, e.g. * libgphoto2 * minicom * ppp * sane-backends * screen * uucp * ... References: http://cvs.fedoraproject.org/viewvc/devel/lockdev http://packages.debian.org/unstable/source/lockdev http://www.pathname.com/fhs/pub/fhs-2.3.html#VARLOCKLOCKFILES + Use Case: + Arduino requires access to /var/lock to run correctly -- openSUSE Feature: https://features.opensuse.org/308360
participants (1)
-
fate_noreply@suse.de