Bug 1031724 - Keyring ccaches should set timeout on the keyring
Summary: Keyring ccaches should set timeout on the keyring
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: krb5
Version: 7.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: rc
: ---
Assignee: Nalin Dahyabhai
QA Contact: Patrik Kis
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-18 15:44 UTC by Simo Sorce
Modified: 2014-06-18 01:08 UTC (History)
3 users (show)

Fixed In Version: krb5-1.11.3-35.el7
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-13 10:17:04 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1053033 0 medium CLOSED regression introduced by krb5-1.11.3-35.el7 2021-02-22 00:41:40 UTC

Description Simo Sorce 2013-11-18 15:44:04 UTC 
The keyring caches do not have an explicit timeout set.
Keyrings should be made to expire when the credentials they contain expire to avoid keeping kernel memory/tmpfs busy with useless data.

It is important on  big systems that have many users and all of them acquire kerberos credentials.

A patch to implement this feature is available upstream in commit: 29e60c5b7ac0980606971afc6fd6028bcf0c7f0f
Comment 3 Ludek Smid 2014-06-13 10:17:04 UTC 
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.
Note You need to log in before you can comment on or make changes to this bug.