[11741] in Kerberos-V5-bugs
Re: [krbdev.mit.edu #6803] Config variable for default ccache
daemon@ATHENA.MIT.EDU (Ken Raeburn via RT)
Fri Oct 15 03:01:04 2010
Mail-followup-to: rt@krbdev.mit.edu
mail-copies-to: never
From: "Ken Raeburn via RT" <rt-comment@krbdev.MIT.EDU>
In-Reply-To: <rt-6803@krbdev.mit.edu>
Message-ID: <rt-6803-33313.6.75875546936346@krbdev.mit.edu>
To: "'AdminCc of krbdev.mit.edu Ticket #6803'":;"'AdminCc of krbdev.mit.edu Ticket #6803'":;@MIT.EDU
Date: Fri, 15 Oct 2010 03:01:02 -0400 (EDT)
Reply-To: rt-comment@krbdev.MIT.EDU
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: krb5-bugs-bounces@mit.edu
Implementing this change would also be a good time to allow setting of the default ccache type -- or the default name-including-type, which is different -- so that a system can be switched to default to keyring ccaches, for example.
A tougher one would be coming up with a mechanism to recommend for sshd, pam, login, and the like to use to generate a new ccache name with a system-wide default type specified in a config file, which may have different type-specific ways of incorporating pty names, session ids, randomly generated strings, etc. Currently, I believe changing the default ccache type for a system means hacking multiple remote-access programs separately?
Ken
_______________________________________________
krb5-bugs mailing list
krb5-bugs@mit.edu
https://mailman.mit.edu/mailman/listinfo/krb5-bugs
