Red Hat Bugzilla – Bug 79615
efax does not appear to use lockdev properly
Last modified: 2007-11-30 17:10:31 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.6 (X11; Linux i686; U;) Gecko/20020830
Description of problem:
efax fails with
efax: 06:41 Error: can't open pre-lock file /var/lock/TMP..02443: Permission denied
unless the /var/lock directory is made world writeable.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
2.attempt to send a fax
Actual Results: efax: 06:41 Error: can't open pre-lock file
/var/lock/TMP..02443: Permission denied
Expected Results: efax should use lockdev (which is sgid lock) to properly lock
the devices. When /var/lock is changed to be world wrietable, the fax sends
fine (which is not ideal from a security point of view, but is certainly a
This is still present in FC2 (efax-0.9-21).
Fedora Core 2 is now maintained by the Fedora Legacy project for
security updates only. If this problem is a security issue, please
reopen and reassign to the Fedora Legacy product. If it is not a
security issue and hasn't been resolved in the current FC3 updates or
in the FC4 test release, reopen and change the version to match.
efax-0.9-22 is FC3 does not attempt to lock anything by default and provides a
-u option to specify a lock file. IMHO it should still be changed to use lockdev.
Closing per lack of response to previous comment. FC3 and FC4 are supported for
security purposes only by Fedora Legacy. If the bug is a security bug, please
reopen and assign to Fedora Legacy. If the bug still occurs in FC5 or FC6,
please reopen and assign to the appropriate version. Thank you.