Relaxed LPRng job submission policy

The LPRng print spooler, as shipped in Red Hat Linux 7.x, accepts all
remote print jobs by default.

With its default configuration, LPRng will accept job submissions from
any host, which is not appropriate in a workstation environment. We
are grateful to Matthew Caron for pointing out this configuration
problem.

The Common Vulnerabilities and Exposures project (cve.mitre.org) has
assigned the name CAN-2002-0378 to this issue.

The updated packages from this advisory change the job submission
policy (in /etc/lpd.perms) so that jobs from remote hosts are refused
by default.

Those running print servers may want to adjust this policy as
appropriate, for example to give access to certain hosts or subnets.
For details on how to do this see the lpd.perms(5) man page.

Since Red Hat Linux 7.1, default installations include ipchains rules
blocking remote access to the print spooler IP port; as a result those
installations already reject remote job submissions. However, Red Hat
Linux 7 machines and any machine upgraded to a later release (as
opposed to
having been freshly installed) will not have ipchains rules in place
by default.

IMPORTANT: There are special instructions for installing this update listed below.

Before applying this update, make sure all previously released errata
relevant to your system have been applied.

To update all RPMs for your particular architecture, run:

rpm -Fvh [filenames]

where [filenames] is a list of the RPMs you wish to upgrade. Only
those
RPMs which are currently installed will be updated. Those RPMs which
are
not installed but included in the list will not be updated. Note that
you
can also use wildcards (*.rpm) if your current directory *only*
contains the
desired RPMs.

Please note that this update is also available via Red Hat Network.
Many
people find this an easier way to apply updates. To use Red Hat
Network,
launch the Red Hat Update Agent with the following command:

up2date

This will start an interactive process that will result in the
appropriate
RPMs being upgraded on your system.

After upgrading, you should check that the new configuration file is
activated. To do this, type the following command:

grep "X NOT SERVER" /etc/lpd.perms

If this commad returns no output, you will need to put the new
configuration file in place by typing:

mv /etc/lpd.perms.rpmnew /etc/lpd.perms

https://www.redhat.com/security/data/cve/CVE-2002-0378.html

LPRng