Public bug reported:

The main reason why Debian/Ubuntu does not enable automatic printer detection
in cups by default is that there is no way to tell apart locally configured
(and thus trusted) printers from those which got detected automatically (and
thus open the possibility of luring someone into printing confidential material
onto a rogue network printer).

E. g. I have a locally configured "local_ps" printer, and an ML-1610 which
comes through cups browsing detection. The print dialog currently looks like
this:

  http://people.ubuntu.com/~pitti/screenshots/print_dialog_gtk.png

the printers look exactly the same, I have no way to tell which ones can be
considered trusted. It would be great to separate the locally configured from
the remotely detected ones:

  |_| Print to file     |
  |=| HP DeskJet 123    | room 10  |
  |=| Samsung Foo Color |          | 
  Automatically detected remote printers:
  |=| ML-1610           | dagobert |

They can be told apart with the CUPS_PRINTER_DISCOVERED flag (see
cups/cups.h).

** Affects: gtk
     Importance: Unknown
         Status: Unknown

** Affects: gtk+2.0 (Ubuntu)
     Importance: Wishlist
         Status: Triaged

** Bug watch added: GNOME Bug Tracker #566782
   http://bugzilla.gnome.org/show_bug.cgi?id=566782

** Also affects: gtk via
   http://bugzilla.gnome.org/show_bug.cgi?id=566782
   Importance: Unknown
       Status: Unknown

** Changed in: gtk+2.0 (Ubuntu)
   Importance: Undecided => Wishlist
       Status: New => Triaged

-- 
Please separate autodetected from locally configured printers
https://bugs.launchpad.net/bugs/314408
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to