Bug 1030689 - krb5_cc(col)_last_change_time() doesn't work as intended with keyring caches
krb5_cc(col)_last_change_time() doesn't work as intended with keyring caches
Status: CLOSED UPSTREAM
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: krb5 (Show other bugs)
7.0
Unspecified Unspecified
low Severity unspecified
: rc
: ---
Assigned To: Robbie Harwood
BaseOS QE Security Team
http://krbdev.mit.edu/rt/Ticket/Displ...
:
Depends On: 1030686
Blocks: 1030688
  Show dependency treegraph
 
Reported: 2013-11-14 18:18 EST by Nalin Dahyabhai
Modified: 2016-11-17 14:10 EST (History)
8 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1030686
Environment:
Last Closed: 2016-11-17 14:10:15 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Nalin Dahyabhai 2013-11-14 18:18:12 EST
+++ 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.