|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0012982||CentOS-7||krb5||public||2017-03-16 17:58||2017-03-16 17:58|
|Priority||normal||Severity||minor||Reproducibility||have not tried|
|Platform||Intel 64 bit||OS||Centos||OS Version||7|
|Target Version||Fixed in Version|
|Summary||0012982: klist needs improvements for KEYRING|
|Description||If your using KEYRING for Kerberos credentials (which seems to be the default for Centos 7), there are some issues with klist:|
1. If KRB5CCNAME is set to a specific cache, e.g. KEYRING:persistent:123:xxxx, klist -l only shows that one cache, even if there are others in the collection. You can argue that this is in some sense correct, but it's misleading.
2. If KRB5CCNAME is set to the collection, e.g. KEYRING:pesistent:123, klist -l shows all the caches, but doesn't show you which is primary. A klist without -l will give you the information on the primary cache, so you can figure out which is primary, but still, you'd expect klist -l to show which of the listed caches is primary.
|Tags||No tags attached.|
|2017-03-16 17:58||hedrick||New Issue|