Bug 157316 - Smbd - cannot connect to CUPS port
Smbd - cannot connect to CUPS port
Product: Fedora
Classification: Fedora
Component: selinux-policy-strict (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Daniel Walsh
Depends On:
  Show dependency treegraph
Reported: 2005-05-10 12:12 EDT by Ivan Gyurdiev
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-05-12 01:16:24 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 Ivan Gyurdiev 2005-05-10 12:12:58 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.7) Gecko/20050416 Fedora/1.0.3-2 Firefox/1.0.3

Description of problem:
Samba denials, generated by connecting from a windows machine.
Port 631 is CUPS - it's probably trying to list attached printers.

audit(1115733990.111:0): avc:  denied  { connect } for  scontext=system_u:system_r:smbd_t tcontext=system_u:system_r:smbd_t tclass=tcp_socket
audit(1115733990.111:0): avc:  denied  { name_connect } for  dest=631 scontext=system_u:system_r:smbd_t tcontext=system_u:object_r:ipp_port_t tclass=tcp_socket

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

How reproducible:
Didn't try

Steps to Reproduce:

Additional info:
Comment 1 Daniel Walsh 2005-05-10 13:29:10 EDT
Are you running NIS without allow_ypbind running?

Why would snmp be attempting to connect to ipp_port?
Comment 2 Ivan Gyurdiev 2005-05-10 13:46:48 EDT
I don't use NIS. This is smbd, not snmp - I think it's just trying to
deal with the [printers] share, so it contacts CUPS.
Comment 3 Daniel Walsh 2005-05-10 14:01:57 EDT
Sorry misread.  Ok I will add perms to allow this?

We used to see apps trying to connect to lpp port all the time when portmap
would return it.

Fixed in policy 1.23.15-4

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