Your message dated Tue, 11 Jan 2022 19:45:50 +0000 with message-id <[email protected]> and subject line Re: Bug#712872: cups: [RFE] Modifying authentication data for a job in the queue has caused the Debian Bug report #712872, regarding cups: [RFE] Modifying authentication data for a job in the queue to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 712872: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712872 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: cups Version: 1.6.2-9 Severity: wishlist -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Some programs (such as Libreoffice) do not provide a way to specify a username and password when printing to a printer that has "AuthInfoRequired username,password" in its printers.conf entry. A job created by such a program will sit in the queue until an administrator removes it. I'd like a way for the administrator to specify authentication values for such a job that has been created without them. Something like: # lpmodify -o username=foo,password 7 Enter value for 'password': ******* Here the given value was used for username, and since no password was specified it was prompted so that it is not visible in the process's command line arguments, nor is it recorded in the user's shell history. - -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (540, 'testing'), (530, 'unstable'), (520, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.9-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages cups depends on: ii cups-client 1.6.2-9 ii cups-common 1.6.2-9 ii cups-daemon 1.6.2-9 ii cups-filters 1.0.34-3 ii cups-ppdc 1.5.3-5 ii cups-server-common 1.6.2-9 ii debconf [debconf-2.0] 1.5.50 ii ghostscript 9.05~dfsg-6.3 ii libavahi-client3 0.6.31-2 ii libavahi-common3 0.6.31-2 ii libc-bin 2.17-3 ii libc6 2.17-3 ii libcups2 1.6.2-9 ii libcupscgi1 1.6.2-9 ii libcupsimage2 1.6.2-9 ii libcupsmime1 1.6.2-9 ii libcupsppdc1 1.6.2-9 ii libgcc1 1:4.8.1-2 ii libstdc++6 4.8.1-2 ii libusb-1.0-0 2:1.0.15-1 ii lsb-base 4.1+Debian12 ii poppler-utils 0.18.4-6 ii procps 1:3.3.4-2 Versions of packages cups recommends: pn avahi-daemon <none> ii colord 0.1.21-4 ii foomatic-filters 4.0.17-1 ii ghostscript-cups 9.05~dfsg-6.3 pn printer-driver-gutenprint <none> Versions of packages cups suggests: ii cups-bsd 1.6.2-9 pn cups-pdf <none> pn foomatic-db-compressed-ppds | foomatic-db <none> pn hplip <none> pn printer-driver-hpcups <none> ii smbclient 2:3.6.15-1 ii udev 175-7.2 - -- debconf information: * cupsys/raw-print: true * cupsys/backend: lpd, socket, usb, snmp, dnssd -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlHC7qkACgkQshl/216gEHiCfQCeLjeAhKPewvt8azJbnuvplhZw vtsAn35rHJS90ctdW/diEyUKVw23l6wn =lw1N -----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---On Thu 20 Jun 2013 at 12:59:37 +0100, Sam Morris wrote: > Package: cups > Version: 1.6.2-9 > Severity: wishlist > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Some programs (such as Libreoffice) do not provide a way to specify a > username and password when printing to a printer that has > "AuthInfoRequired username,password" in its printers.conf entry. > > A job created by such a program will sit in the queue until an > administrator removes it. > > I'd like a way for the administrator to specify authentication values > for such a job that has been created without them. Something like: > > # lpmodify -o username=foo,password 7 > Enter value for 'password': ******* > > Here the given value was used for username, and since no password was > specified it was prompted so that it is not visible in the process's > command line arguments, nor is it recorded in the user's shell history. In spite of my input on 10 Sep 2021, progress on this report has stalled. It is difficult to envisage a resolution being reached. Hence closing. Regards, Brian.
--- End Message ---
