| Summary: | Change default ccache name to DIR:/run/user/%{uid}/krb5cc | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Hartmut Goebel <h.goebel> |
| Component: | RPM Packages | Assignee: | Guillaume Rousse <guillomovitch> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Normal | CC: | nic |
| Version: | Cauldron | Keywords: | NEEDINFO, Triaged |
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | krb5-1.11.1-1.2.mga3.src.rpm | CVE: | |
| Status comment: | |||
|
Description
Hartmut Goebel
2013-10-24 20:51:54 CEST
Manuel Hiebel
2013-10-24 22:58:04 CEST
Keywords:
(none) =>
Triaged This does change both the location and the type of the default credential cache, for reasons explained here: http://fedoraproject.org/wiki/Features/KRB5DirCache http://fedoraproject.org/wiki/Features/KRB5CacheMove Moreover, that's for fedora 18 and 19 only, fedora 20 seems to use kernel keyring directly, backported from incoming 1.12 release: http://pkgs.fedoraproject.org/cgit/krb5.git/tree/krb5.spec http://k5wiki.kerberos.org/wiki/Projects/Keyring_collection_cache That's a bit more invasive than I'm willing to test right now... What's the status in current cauldron? Keywords:
Junior_job =>
NEEDINFO The lack of comment since 2013 is quite explicit: no change ever occurred. No further comment so closed Status:
NEW =>
RESOLVED |