RT RT/krbdev.mit.edu: Ticket #7766 Keyring last_change_time implementation isn't useful Signed in as guest.
[Logout]

[Home] [Search] [Configuration]

[Display] [History] [Basics] [Dates] [People] [Links] [Jumbo]

 
 

 The Basics  
Id
7766
Status
open
Worked
0 min
Priority
0/0
Queue
krb5
 

 Keyword Selections  
Component
Tags
Version_reported
Version_Fixed
Target_Version
 

 Relationships  
Depends on:
Depended on by:
Parents:
Children:

Refers to:
Referred to by:
 
 Dates  
Created: Thu Nov 14 18:02:48 2013
Starts: Not set
Started: Thu Nov 14 18:02:57 2013
Last Contact: Not set
Due: Not set
Updated: Thu Nov 14 18:02:57 2013 by ghudson
 

 People  
Owner
 Nobody
Requestors
 ghudson@mit.edu
Cc
 
AdminCc
 
 

 More about Greg Hudson  
Comments about this user:
No comment entered about this user
This user's 25 highest priority tickets:
 

History   Display mode: [Brief headers] [Full headers]
      Thu Nov 14 18:02:48 2013  ghudson - Ticket created    
     
Subject: Keyring last_change_time implementation isn't useful

The cc_keyring.c implementation of last_change_time from r20743 records
the last change time in memory only, so all you find out is the last time
that particular handle was resolved, initialized, or stored into.  You
don't find out anything about the underlying cache.

The kernel key API does not appear to have timestamps (we should verify
this), so fixing this will probably require adding a new key to the cache
keyring.


Download (untitled) 430b
      Thu Nov 14 18:02:57 2013  ghudson - Status changed from new to open