Bug 476232 - gtk2 cups printer backend does not attempt SO_PEERCRED authentication
Summary: gtk2 cups printer backend does not attempt SO_PEERCRED authentication
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: gtk2
Version: 5.4
Hardware: All
OS: Linux
low
high
Target Milestone: rc
: ---
Assignee: Benjamin Otte
QA Contact: desktop-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-12-12 16:45 UTC by Dan Astoorian
Modified: 2014-06-09 14:04 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-02 13:05:15 UTC
Target Upstream Version:
Embargoed:
djast: needinfo-


Attachments (Terms of Use)

Description Dan Astoorian 2008-12-12 16:45:38 UTC
Description of problem:
When the libprintbackend-cups.so printer backend for gtk2 receives a HTTP_UNAUTHORIZED response from the CUPS server, it emits the warning "NOT IMPLEMENTED: We need to prompt for authorization".  However, since CUPS can use peercred authentication, it is possible to authenticate without additional prompting: libprintbackend-cups.so should call cupsDoAuthentication() and retrying instead of assuming that no authentication is possible and giving up immediately.

Version-Release number of selected component (if applicable):
gtk2-2.10.4-20.el5

How reproducible:
Always

Steps to Reproduce:
1. Set "AuthType Basic" in the <Location /> section of /etc/cups/cupsd.conf and reload cupsd ("/sbin/service cups reload")
2. Run firefox (or another GTK application which prints using the gtk2 cups print backend)
3. Select File -> Print to attempt to print a page.
  
Actual results:
No printers are listed in the dialog, and the message "** (Gecko:[...]): WARNING **: NOT IMPLEMENTED: We need to prompt for authorization" is written repeatedly to stderr.


Expected results:
The application should authenticate successfully via peercred authentication.

Additional info:

Comment 3 RHEL Program Management 2014-03-07 12:42:03 UTC
This bug/component is not included in scope for RHEL-5.11.0 which is the last RHEL5 minor release. This Bugzilla will soon be CLOSED as WONTFIX (at the end of RHEL5.11 development phase (Apr 22, 2014)). Please contact your account manager or support representative in case you need to escalate this bug.

Comment 4 RHEL Program Management 2014-06-02 13:05:15 UTC
Thank you for submitting this request for inclusion in Red Hat Enterprise Linux 5. We've carefully evaluated the request, but are unable to include it in RHEL5 stream. If the issue is critical for your business, please provide additional business justification through the appropriate support channels (https://access.redhat.com/site/support).


Note You need to log in before you can comment on or make changes to this bug.