Bug 468729

Summary: krb5_cc_new_unique() fails
Product: Red Hat Enterprise Linux 5 Reporter: Tim Waugh <twaugh>
Component: krb5Assignee: Nalin Dahyabhai <nalin>
Status: CLOSED ERRATA QA Contact: BaseOS QE <qe-baseos-auto>
Severity: medium Docs Contact:
Priority: high    
Version: 5.2CC: jplans, mkoci, syeghiay, ykopkova, zmraz
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: 1.6.1-30.el5 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-01-20 22:10:25 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 409121    
Attachments:
Description Flags
test for exercising krb5_cc_new_unique() none

Description Tim Waugh 2008-10-27 17:52:10 UTC
Description of problem:
In order to have functioning Kerberos support in CUPS the krb5_cc_new_unique() function in krb5 must be fixed to avoid this bug:
  http://krbdev.mit.edu/rt/Ticket/Display.html?id=5624

Version-Release number of selected component (if applicable):
krb5-1.6.1-29.el5

Comment 3 Nalin Dahyabhai 2008-10-27 21:07:39 UTC
Note to self: also needs to incorporate fixes for RT#5708, which is a bit larger.

Comment 6 Nalin Dahyabhai 2008-10-28 18:17:57 UTC
Created attachment 321715 [details]
test for exercising krb5_cc_new_unique()

Tim tells me that the release notes for the cups update includes this nugget: "Note that this requires a recent version of MIT Kerberos with a working krb5_cc_new_unique() function or Heimdal Kerberos."

This program creates a new unique ccache, copies the contents of the default ccache into the new one, runs 'klist' for both, and then exits.

Comment 13 errata-xmlrpc 2009-01-20 22:10:25 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2009-0234.html