Bug 10718 - lpr-0.48: When hostname is uppercased, remote lprm stops working.
lpr-0.48: When hostname is uppercased, remote lprm stops working.
Product: Red Hat Linux
Classification: Retired
Component: lpr (Show other bugs)
All Linux
medium Severity high
: ---
: ---
Assigned To: Bernhard Rosenkraenzer
Depends On:
  Show dependency treegraph
Reported: 2000-04-11 02:13 EDT by Aleksey Nogin
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-04-11 02:28:58 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Aleksey Nogin 2000-04-11 02:13:33 EDT
lprm-0.48 only allows non-root users to remove jobs from the same host from
which the print job was submitted. However, the testing is really screwed
up and when it fails, lprm stops working...

As I understand it, lpr records the hostname of the machine where the jobs
is submitted and compares it to the reverse-DNS of the IP submitting the
lprm command _lowercased_. Result:

1) Hostname = rev-DNS, but includes upper-case letters -> check fails, lprm
does not work.
2) Hostname != rev-DNS -> check fails, lprm does not work.

While (2) is understandable for security reasons, (1) is really annoying
(especially after I've spent _lots_ of time trying to figure the whole
thing out).

P.S. I tried it only with RH-5.2 runnin on both client and daemon, but I
expect result to be the same on all other versions of RH, on which the
lpr-0.48 update was installed.
Comment 1 Aleksey Nogin 2000-04-11 02:14:59 EDT
P.P.S. It would be nice to be able to get rid of the whole testing using some
printcap flag.
Comment 2 Aleksey Nogin 2000-04-11 02:20:59 EDT
Related problem: bug #387
Comment 3 Aleksey Nogin 2000-04-11 02:28:59 EDT
P3.S. The "Permission denied" error message is _extremely_ uninformative. I
would suggest something along the lines "can only be removed from <hostname>".
Comment 4 Bernhard Rosenkraenzer 2000-07-17 11:21:13 EDT
This is fixed in rawhide with the move to LPRng.

Note You need to log in before you can comment on or make changes to this bug.