Comment 6 for bug 653132

Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

Tim, I tried the following:

----------
till@till:~$ sudo su - test
[sudo] password for till:
test@till:~$ /usr/sbin/lpadmin -p testqueue -E -v /dev/null
lpadmin: Forbidden
test@till:~$ /usr/sbin/lpadmin -U till -p testqueue -E -v /dev/null
Password for till on localhost?
lpadmin: Unauthorized
test@till:~$ /usr/sbin/lpadmin -U till -p testqueue -E -v /dev/null
Password for till on localhost?
test@till:~$ lpstat -v testqueue
device for testqueue: /dev/null
test@till:~$ exit
logout
till@till:~$ lpadmin -x testqueue
till@till:~$
----------

"till" is in the "lpadmin"group, "test" not. On the first "/usr/sbin/lpadmin -U till ..." command I simply pressed Enter on the password prompt and the command exited immidiately, on the second command I entered the correct password and the queue got created. Entering a wrong, non-empty password leads to a new password prompt, also entering nothing on the new prompt closes lpadmin.

So CUPS seems to behave correctly.