Bug 1030689 - krb5_cc(col)_last_change_time() doesn't work as intended with keyring caches
Summary: krb5_cc(col)_last_change_time() doesn't work as intended with keyring caches
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: krb5
Version: 7.0
Hardware: Unspecified
OS: Unspecified
low
unspecified
Target Milestone: rc
: ---
Assignee: Robbie Harwood
QA Contact: BaseOS QE Security Team
URL: http://krbdev.mit.edu/rt/Ticket/Displ...
Whiteboard:
Depends On: 1030686
Blocks: 1030688
TreeView+ depends on / blocked
 
Reported: 2013-11-14 23:18 UTC by Nalin Dahyabhai
Modified: 2016-11-17 19:10 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1030686
Environment:
Last Closed: 2016-11-17 19:10:15 UTC
Target Upstream Version:

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

Description Nalin Dahyabhai 2013-11-14 23:18:12 UTC 
+++ This bug was initially created as a clone of Bug #1030686 +++

The krb5_ccc_last_change_time() and krb5_cccol_last_change_time() functions are meant to provide the caller with the last time a particular cache or cache collection was modified.  Their implementation for KEYRING caches is such that different processes will get different results, if they get anything other than 0.  Since we've been looking at using these functions to monitor user caches and check for impending expiration, we need to fix them.
Note You need to log in before you can comment on or make changes to this bug.