2017-08-18 16:16 UTC

View Issue Details Jump to Notes ]
IDProjectCategoryView StatusLast Update
0012982CentOS-7krb5public2017-03-16 17:58
Reporterhedrick 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusnewResolutionopen 
PlatformIntel 64 bitOSCentosOS Version7
Product Version7.3.1611 
Target VersionFixed in Version 
Summary0012982: klist needs improvements for KEYRING
DescriptionIf 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.
TagsNo tags attached.
abrt_hash
URL
Attached Files

-Relationships
+Relationships

-Notes
There are no notes attached to this issue.
+Notes

-Issue History
Date Modified Username Field Change
2017-03-16 17:58 hedrick New Issue
+Issue History