This is what Fedora >18 does. See .spec-file in ftp://ftp.icm.edu.pl/vol/rzm2/linux-fedora-secondary/updates/testing/19/SRPMS/krb5-1.11.3-1.fc19.src.rpm Storing the credential-cache in /run/user has the benefit, that /tmp will not be cluttered with user-related files. Further this seams to be the place to store ephemeral user data. From fedoras .spec-file: ....8<--- %if 0%{?fedora} > 18 || 0%{?rhel} > 6 DEFCCNAME=DIR:/run/user/%%{uid}/krb5cc; export DEFCCNAME %endif [...] * Fri Apr 12 2013 Nalin Dahyabhai <nalin@redhat.com> 1.11.1-9 - move the compiled-in default ccache location from the previous default of FILE:/tmp/krb5cc_%%{uid} to DIR:/run/user/%%{uid}/krb5cc (part of #949588) ....8<---
Keywords: (none) => TriagedAssignee: bugsquad => guillomovitch
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 => NEEDINFOTarget Milestone: Mageia 4 => ---Severity: minor => enhancement
The lack of comment since 2013 is quite explicit: no change ever occurred.
No further comment so closed
Status: NEW => RESOLVEDCC: (none) => nicResolution: (none) => OLD