Bug 848226 - delegation acceptors will need to store delegated creds in locations other than /tmp
Summary: delegation acceptors will need to store delegated creds in locations other th...
Alias: None
Product: Fedora
Classification: Fedora
Component: krb5-appl
Version: 19
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Roland Mainz
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2012-08-14 23:06 UTC by Nalin Dahyabhai
Modified: 2015-09-08 17:27 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2015-02-17 14:24:50 UTC
Type: Bug

Attachments (Terms of Use)

Description Nalin Dahyabhai 2012-08-14 23:06:23 UTC
Description of problem:

As part of the Fedora 18 features https://fedoraproject.org/wiki/Features/KRB5CacheMove and https://fedoraproject.org/wiki/Features/KRB5DirCache, the various servers in krb5-appl-servers which accept delegated credentials and store them in credential caches for users will need to be taught to put them in a different location.

Specifically, they'll go in /run/user/$UID, and preferably in a "DIR" type ccache rather than the "FILE" type which is currently used.

If that fails for some reason, falling back to the current behavior is going to likely be better than nothing.

Version-Release number of selected component (if applicable):

How reproducible:
Use Kerberos-aware telnet/rsh/rlogin with credential forwarding switched on to run "klist" on the server.  (FTP, too, though it's not quite as easy to verify.)  The location should be under /run/user/$UID (assuming /run/user exists), and preferably be of type "DIR" rather than "FILE".

Comment 1 Fedora End Of Life 2013-04-03 16:28:06 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:

Comment 2 Fedora Admin XMLRPC Client 2014-09-19 13:01:12 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 3 Fedora End Of Life 2015-01-09 17:19:20 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Fedora End Of Life 2015-02-17 14:24:50 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.