[Bug 543549] New: CUPS 'Browsing Mode' is enabled by default
http://bugzilla.novell.com/show_bug.cgi?id=543549 Summary: CUPS 'Browsing Mode' is enabled by default Classification: openSUSE Product: openSUSE 11.2 Version: Milestone 8 Platform: All OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Printing AssignedTo: jsmeix@novell.com ReportedBy: thomas@cupracer.de QAContact: jsmeix@novell.com Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9.0.14) Gecko/2009090900 SUSE/3.0.14-0.1.2 Firefox/3.0.14 I'm thinking about the following issue whenever I install a fresh openSUSE, so I think that it's time for a bug report: While setting up CUPS within the installation an configuration procedure, I stumble over the 'Browsing Mode', which is enabled by default. I think that it should be disabled, so that there's no interchange between the local and a remote CUPS server. Surely, there's a SuSEFirewall that prevents the communication, but if the firewall is turned off, the communication begins. In fact, an attacker could provide our local CUPS with wrong information to get copies of secret documents (or whatever). The user should enable this option explicitely if he's interested in this feature. openSUSE 11.2 M8 even has the sshd disabled by default. So why should there still exist a network-activated daemon that is able to modify the systems configuration (= list of printers) without making the user aware of it? Reproducible: Always Steps to Reproduce: 1. install openSUSE 11.2 (build0307) up to "hardware configuration" 2. select "Printer" to start the CUPS configuration 3. select ~ "network printing" and find the Browsing mode option (Sorry, currently I just have the german version installed an don't know the right translation for these menus) Actual Results: Browsing Mode is turned on by default. Expected Results: Browsing Mode should be turned off by default. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=543549 User thomas@cupracer.de added comment http://bugzilla.novell.com/show_bug.cgi?id=543549#c1 Thomas Schulte <thomas@cupracer.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution| |INVALID --- Comment #1 from Thomas Schulte <thomas@cupracer.de> 2009-10-01 10:20:26 MDT --- I'm sorry, I think that I wasn't all there when I opened this bug. :-) I just realized that the browsing mode gets disabled when no IP address of another CUPS server is given in the setup dialog. This bug can be closed. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=543549 User jsmeix@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=543549#c2 --- Comment #2 from Johannes Meixner <jsmeix@novell.com> 2009-10-01 11:14:28 MDT --- FYI regarding "an attacker could provide our local CUPS with wrong information" see the "print job phishing" thread on the cups.general Newsgroup respectively the cups@easysw.com mailing list: http://www.cups.org/newsgroups.php?gcups.general+T+Q"print+job+phishing" Therefore see http://en.opensuse.org/SDB:CUPS_in_a_Nutshell in the "Configuring CUPS in the Network" section what I wrote "Regarding firewall". -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=543549 User thomas@cupracer.de added comment http://bugzilla.novell.com/show_bug.cgi?id=543549#c3 --- Comment #3 from Thomas Schulte <thomas@cupracer.de> 2009-10-01 12:35:59 MDT --- Thanks, Johannes! This was very informative to me. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com