Bug 131745 - firewall doesn't allow for printer service discovery
firewall doesn't allow for printer service discovery
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: system-config-securitylevel (Show other bugs)
3
All Linux
medium Severity medium
: ---
: ---
Assigned To: Paul Nasrat
:
Depends On:
Blocks: 131589
  Show dependency treegraph
 
Reported: 2004-09-03 16:29 EDT by Bryan W Clark
Modified: 2007-11-30 17:10 EST (History)
3 users (show)

See Also:
Fixed In Version: 1.4.10-1
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-10-13 15:42:21 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Bryan W Clark 2004-09-03 16:29:39 EDT
The GNOME Printing utilities now auto-populate the print dialogs with
printers found through service discovery.  For a Desktop install we
definitely need to have an option in the firewall tool for allowing
print service discovery. [x] CUPS (Printing)

This service also needs be checked off by default on desktop installs.
 Perhaps restricted to the local subnet since I believe the service
discover cannot go beyond that anyway.

CC'ing Walters and Matthias on this one too.
Comment 1 Bill Nottingham 2004-09-03 18:43:31 EDT
Do we even want to offer the option of blocking it?
Comment 2 Bryan W Clark 2004-09-07 11:24:39 EDT
My major concern here is that the print detection system works.

Because of the interference from the firewall I assumed that this port
had been shutoff for security reasons.  However if we feel that always
opening up the firewall for CUPS isn't a terrible security threat,
then I'm fine with that since my major concern is taken care of.  It
will also give much less room for error in the firewall/printing setup.
Comment 3 Paul Nasrat 2004-09-14 05:55:28 EDT
I'm happy to do either - though have I missed the screen/string freeze
for FC3t2.  In which case I can open by default and then when I
improve the add/remove trusted services ui for bug #124161 you'll get
better configuration.

This sound like a plan?
Comment 4 Colin Walters 2004-09-14 09:07:09 EDT
That sounds reasonable, but we definitely have to document that the
firewall allows this by default, since the current default is to deny
*everything* except a few ICMP packets, right?
Comment 5 Bryan W Clark 2004-09-14 13:39:58 EDT
Sounds reasonable to me too.  Lets go with that.
Comment 6 Bryan W Clark 2004-09-24 16:24:12 EDT
this is a similar issue to bug 133478
Comment 7 Bryan W Clark 2004-10-13 11:39:24 EDT
paul, can we commit to opening this up and fix the UI issues later.
Comment 8 Paul Nasrat 2004-10-13 12:47:39 EDT
CUPS browsing should be enabled in latest s-c-securitylevel (you will
have to update s-c-securitylevel-tui).  A rebuild for another issue
pulled it in so it just wasn't in the %changelog.

Can someone with a cups setup test with configuring firewall with 
system-config-securitylevel-tui-1.4.9-1
Comment 9 Bill Nottingham 2004-10-13 15:42:21 EDT
Works for me with 1.4.10-1.

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