From: Till Kamppeter <till.kamppeter@gmail.com>
To: Alexander Wauck <alex.wauck@gmail.com>,
Per Hermansson <hermansson.per@bredband.net>,
printing-architecture@lists.linux-foundation.org,
Lars Uebernickel <larsuebernickel@gmx.de>
Subject: Re: [Printing-architecture] Common Printing Dialog and job being rejected by CUPS
Date: Mon, 17 Aug 2009 12:47:50 +0200 [thread overview]
Message-ID: <4A893556.8000707@gmail.com> (raw)
In-Reply-To: <4A89337B.3040701@gmail.com>
CUPS bug report:
http://www.cups.org/str.php?L3291
Till
Till Kamppeter wrote:
> [ Mainly for Alex and Lars, I have discussed this with Per on IRC ]
>
> Per, thanks also for your quick implementation of marking printers as
> stopped, rejecting jobs, or needing authentication.
>
> For testing, I have added
>
> AuthInfoRequired username,password
>
> to one of the print queue entries in /etc/cups/printers.conf and
> restarted CUPS. This printer shows correctly in your dialog that
> authentication is required.
>
> Problem is the following: I printed through this printer successfully
> from your dialog, not getting asked for a password. As I am privileged
> user (in "lpadmin" group), I tried also to print via
>
> sudo su nobody -c 'lpr -P 2 ~/.bashrc'
>
> Then I get only asked for my password to execute sudo, but CUPS does not
> ask for the password of "nobody". It simply printes the job.
>
> This looks like that
>
> AuthInfoRequired username,password
>
> in /etc/cups/printers.conf makes CUPS reporting that, but in reality it
> does not need it.
>
> Per is using standard CUPS APIs
> (http://www.cups.org/documentation.php/api-cups.html#PRINTERS_AND_CLASSES)
> to report whether a printer needs authentication. Seems that CUPS has a
> bug here. Per will report it to CUPS upstream.
>
> Till
prev parent reply other threads:[~2009-08-17 10:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-15 12:31 [Printing-architecture] Common Printing Dialog and job being rejected by CUPS Till Kamppeter
2009-08-16 16:06 ` Till Kamppeter
2009-08-17 10:39 ` Till Kamppeter
2009-08-17 10:47 ` Till Kamppeter [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A893556.8000707@gmail.com \
--to=till.kamppeter@gmail.com \
--cc=alex.wauck@gmail.com \
--cc=hermansson.per@bredband.net \
--cc=larsuebernickel@gmx.de \
--cc=printing-architecture@lists.linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.