Hrm.. I could have sworn I changed that message to refer you to the cups
package instead if it is still an issue.
** Package changed: cupsys (Ubuntu) => cups (Ubuntu)
** Changed in: cups (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/345015
Title:
CUPS SNMP should not scan the entire local subnet by default
Status in “cups” package in Ubuntu:
New
Bug description:
Binary package hint: cupsys
There is a bug in Launchpad somewhere where users where complaining
that the SNMP backend in CUPS was disabled. The bug was resolved in
Intrepid, and it does indeed work now.
Unfortunately, it works a bit too well for many enterprise users.
In Intrepid, CUPS will by default, scan the entire local subnet of the
host for printers responding to SNMP. In the enterprise, this sets
off many alarms on various NIDS and firewalls.
I think maybe a happy medium would be to leave the SNMP backend
enabled, so that users can easily set it up, but limit the SNMP
polling to just the localhost.
This can be done by changing /etc/cups/snmp.conf to read
Address 127.0.0.1
instead of
Address @LOCAL
This particular problem caught me, so I wrote a blog post about it. I
have received quite a few comments from other enterprise users
thanking me for the tip. My blog is very low traffic, the fact that
it has any comments at all shows it's affecting quite a few people.
http://www.sysadminsjourney.com/2008/11/05/disable-snmp-printer-
scanning-in-ubuntu-intrepid
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/345015/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
