Bug 605367

Summary: Stop breaking GSS sealed connections at orioginal credentials expiration time
Product: Red Hat Enterprise Linux 5 Reporter: Simo Sorce <ssorce>
Component: krb5Assignee: Nalin Dahyabhai <nalin>
Status: CLOSED ERRATA QA Contact: BaseOS QE Security Team <qe-baseos-security>
Severity: medium Docs Contact:
Priority: low    
Version: 5.5CC: dpal, jplans, selsky
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: krb5-1.6.1-44.el5 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 605366 Environment:
Last Closed: 2011-01-13 23:53:13 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: 605366    
Bug Blocks:    

Description Simo Sorce 2010-06-17 18:20:01 UTC
+++ This bug was initially created as a clone of Bug #605366 +++

The current behaviot of the GSSAPI library is to break GSS wrap/unwrap operations when the original ticket, used to set up the connection, expires.

Recently upstream has finally decided that this is not useful and has committed changes to trunk to change this behaviour. Applications can still query GSSAPI and tear down the connection when the original ticket expires if they want so.

We should backport these changes in RHEL 6 as this was a popular request from many stakeholders.

--- Additional comment from ssorce on 2010-06-17 14:18:27 EDT ---

Upstream bug:
http://krbdev.mit.edu/rt/Ticket/Display.html?id=6739
(Includes pointers to the patches needed)

Comment 1 Simo Sorce 2010-06-17 18:20:41 UTC
It would be appropriate to change it for RHEL 5 too if possible.

Comment 6 errata-xmlrpc 2011-01-13 23:53:13 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-2011-0098.html