Bug 605366 - Stop breaking GSS sealed connections at orioginal credentials expiration time
Summary: Stop breaking GSS sealed connections at orioginal credentials expiration time
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: krb5 (Show other bugs)
(Show other bugs)
Version: 6.0
Hardware: All Linux
Target Milestone: rc
: ---
Assignee: Nalin Dahyabhai
QA Contact: Zbysek MRAZ
Depends On:
Blocks: 605367
TreeView+ depends on / blocked
Reported: 2010-06-17 18:17 UTC by Simo Sorce
Modified: 2016-01-22 17:07 UTC (History)
5 users (show)

Fixed In Version: krb5-1.8.2-2.el6
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 605367 (view as bug list)
Last Closed: 2010-11-10 21:01:10 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Simo Sorce 2010-06-17 18:17:09 UTC
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.

Comment 1 Simo Sorce 2010-06-17 18:18:27 UTC
Upstream bug:
(Includes pointers to the patches needed)

Comment 2 RHEL Product and Program Management 2010-06-17 18:33:17 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for

Comment 6 releng-rhel@redhat.com 2010-11-10 21:01:10 UTC
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.

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