papercuts-ninja team mailing list archive
-
papercuts-ninja team
-
Mailing list archive
-
Message #01246
[Bug 314408] Re: Please separate automatically discovered remote printers from locally configured printers
** Changed in: gtk+3.0 (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Papercuts
Ninjas, which is a bug assignee.
https://bugs.launchpad.net/bugs/314408
Title:
Please separate automatically discovered remote printers from locally
configured printers
Status in GTK+ GUI Toolkit:
New
Status in One Hundred Papercuts:
Triaged
Status in Qt:
New
Status in “gtk+3.0” package in Ubuntu:
In Progress
Status in “qt4-x11” package in Ubuntu:
Triaged
Bug description:
The main reason why Debian/Ubuntu does not enable automatic use of
network printers broadcasted by remote CUPS servers by default is that
there is no way to tell apart locally configured (and thus trusted)
printers from those which got advertized by remote CUPS servers (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
configured on a remote server which appears 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 |
Locally configured printers:
|=| HP DeskJet 123 | room 10 |
|=| Samsung Foo Color | |
Automatically detected remote printers:
|=| ML-1610 | dagobert |
Locally configured and automatically discovered remote printers can be
told apart with the CUPS_PRINTER_DISCOVERED flag (see cups/cups.h).
To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/314408/+subscriptions