Package: lockdev Severity: important SVR4 locks are named using the device major and minor numbers.
For example, /var/lock/LCK.003.000 (/dev/hda). However, the dev_t number might be the same for both a character and block device. This has the implication that locking a block device might also unintentionally (or intentionally, if abused), cause a denial of service by coincidentally locking a character device with the same number (and vice-versa). I'm not sure how standardised the SVR4 locking scheme is, but including a 'c' or 'b' in the lock name would prevent this happening, for example: /var/lock/LCK.C.003.000 or /var/lock/LCK.003.000c The naming scheme should really be standardised by the FHS. I've left this as "important", but there are security implications that might justify raising the severity. Regards, Roger -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (990, 'unstable') Architecture: powerpc (ppc) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.13.1 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
