Description of problem: libutempter fails because of wrong directory permissions on /usr/libexec/libutempter directory Version-Release number of selected component (if applicable): libutempter-1.1.4-4 How reproducible: Always Steps to Reproduce: 1. rpm -qvl libutempter | grep /usr/libexec/utempter 2. as non-root user "rsh host xterm' or similar Actual results: 1. directory has 04710 permissions 2. no entry made in /var/run/utmp etc Expected results: 1. directory should have 04711 permission 2. entry should be made in /var/run/utmp and /var/log/wtmp Additional info: Running xterm as non-root and with no setuid bits set on xterm means that xterm will run as an ordinary user and will not be able to read or execute anything in /usr/libexec/utempter. Of course, xterm could be setgid, but it isn't. Or every users could be added to utempter group but that is tedious. This used to work ok when utempter binary was in /usr/sbin. Why the change? The actual utempter binary is still world executable so setting its directory to non-world-executable would seem rather strange. It would be best if utempter (and xterm) were distributed so that they both worked properly without further (undocumented) configuration. It would also help if, at the very minimum, the libutempter distribution contained some useful documentation if it was a design choice to not make the libexec directory world executable. How about a manual entry for utempter?
Please make sure you have a up-to-date system before reporting any bugs. The latest version (libutempter-1.1.5-1.fc8 in F8) should not have these issues. If you have other problems please reopen or file another bug report.
Please do not release software that doesn't work.