Bug 5669
| Summary: | rec.1 link in sox-12.16-3 is incorrect. | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | dopey |
| Component: | sox | Assignee: | Bill Nottingham <notting> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | |
| Severity: | low | Docs Contact: | |
| Priority: | medium | ||
| Version: | 6.1 | CC: | chauvin, dottedquad, j, jeff, jgotts, mrsam, rsousa, rvokal |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 1999-10-07 14:25:34 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
dopey
1999-10-07 04:03:06 UTC
Fixed in sox-12.16-4, in Raw Hide. *** Bug 5807 has been marked as a duplicate of this bug. *** Standard precompiled package sox contains invalid soft link /usr/man/man1/rec.1 -> /var/tmp/sox-root/usr/man/man1/play.1 *** Bug 6177 has been marked as a duplicate of this bug. *** This is minor, but after upgrading from 6.0 to 6.1 the symbolic link for the 'rec' man page was broken. In /usr/man/man1, I had lrwxrwxrwx 1 root root 37 Oct 17 21:24 rec.1 -> /var/tmp/sox-root/usr/man/man1/play.1 (the above should be read as all one line). ---- The interesting thing is that this manifested itself a week later in mail to root about the failure of run-parts on cron.weekly. The entire message was: From: root.tntech.edu (Cron Daemon) To: root.tntech.edu Subject: Cron <root@norden> run-parts /etc/cron.weekly Read file error: ./rec.1 No such file or directory This also points up a weakness in /usr/sbin/makewhatis, in that it doesn't do a very good job of error reporting. It doesn't even report its own name (so I had to start by looking in cron.weekly) nor does it report the full path to the offending file. Hope this helps. Let me know if you'd like me to submit a patch and I'll work one up for you. *** Bug 6302 has been marked as a duplicate of this bug. *** Contents of sox-12.16-3.i386.rpm: lrwxrwxrwx root root 37 Sep 24 17:13 /usr/man/man1/rec.1 -> /var/tmp/sox-root/usr/man/man1/play.1 This generates an error from makewhatis, running weekly off cron. : The interesting thing is that this manifested itself a week : later in mail to root about the failure of run-parts on : cron.weekly. The entire message was: Note that there are potential security considerations here. An attacker can easily create the file /var/tmp/sox-root/usr/man/man1/play.1, then have its contents read by makewhatis, which is running as root. *** Bug 6378 has been marked as a duplicate of this bug. *** /usr/man/man1/rec.1 is a link to /var/tmp/sox-root/usr/man/man1/play.1 *** Bug 6590 has been marked as a duplicate of this bug. *** in the sox package, the following gets installed: % ls -l /usr/man/man1/rec.1 lrwxrwxrwx 1 root root 37 Oct 23 00:38 /usr/man/man1/rec.1 -> /var/tmp/sox-root/usr/man/man1/play.1 this obviously isn't quite what was intended ... *** Bug 6706 has been marked as a duplicate of this bug. *** The symlink at /usr/man/man1/rec.1 is incorrectly set to somewhere in /var/tmp/ it should simply be set to play.1 instead of the strange hard address it was given on whatever machine built the sox package. *** Bug 6814 has been marked as a duplicate of this bug. *** /usr/man/man1/rec.1 points to /var/tmp/sox-root/usr/man/man1/play.1 I believe it should point to /usr/man/man1/play.1 *** Bug 6844 has been marked as a duplicate of this bug. *** Bad symlink to file "play.1" causes makewhatis to report an error. In /usr/man/man1/: lrwxrwxrwx rec.1 -> /var/tmp/sox-root/usr/man/man1/play.1 should be: lrwxrwxrwx rec.1 -> play.1 *** Bug 7213 has been marked as a duplicate of this bug. *** *** Bug 7403 has been marked as a duplicate of this bug. *** *** Bug 7383 has been marked as a duplicate of this bug. *** *** Bug 8336 has been marked as a duplicate of this bug. *** *** Bug 8372 has been marked as a duplicate of this bug. *** *** Bug 10243 has been marked as a duplicate of this bug. *** *** Bug 15602 has been marked as a duplicate of this bug. *** |