Bug 137955 - CUPS ignores Listen directive for UDP port
CUPS ignores Listen directive for UDP port
Product: Fedora
Classification: Fedora
Component: cups (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Tim Waugh
Depends On:
  Show dependency treegraph
Reported: 2004-11-03 01:22 EST by Albert Strasheim
Modified: 2007-11-30 17:10 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-11-03 05:47:42 EST
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 Albert Strasheim 2004-11-03 01:22:08 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.3)
Gecko/20041026 Firefox/1.0RC1

Description of problem:
I configured my printer with system-config-printer. It added the
following lines to /etc/cups/cupsd.conf:

<Location /printers/hp4plus>
Order Deny,Allow
Deny From All
Allow From
AuthType None
<Location />
Order Deny,Allow
Deny From All
Allow From
Browsing On
BrowseProtocols cups
BrowseOrder Deny,Allow
BrowseAllow from @LOCAL

The configuration file contains no other Listen or Port directives.

However, according to netstat:

tcp        0      0 *    LISTEN      
udp        0      0   *                

CUPS seems to be ignoring the Listen directive for its UDP port. I
don't know if this is related to browsing, but specifying a
BrowseAddress doesn't make a difference (CUPS still binds to all

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Configure CUPS with system-config-printer.
2. netstat -na | grep 631

Actual Results:  CUPS TCP port listens to specified interface and
port, but UDP port listens to all interfaces on the specified port.

Expected Results:  CUPS should only listen on the specified interface.

Additional info:
Comment 1 Tim Waugh 2004-11-03 04:31:58 EST
The Listen directive is for IPP connections (i.e. TCP).  The
BrowseAllow/BrowseDeny directives are what you want.
Comment 2 Albert Strasheim 2004-11-03 05:21:30 EST
The CUPS UDP port listens on all interfaces regardless of the 
BrowseAllow and BrowseDeny directives. I don't think this is as 
secure as it can be.

CUPS should either use the Listen directive and listen on those 
interfaces for both TCP and UDP or figure out which interfaces to 
listen on using the Browse directives (probably tricky).
Comment 3 Tim Waugh 2004-11-03 05:47:42 EST
Tracking this upstream:


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