Return-Path: Received: from mailhub-auth-1.mit.edu (MAILHUB-AUTH-1.MIT.EDU [18.9.21.35]) by krbdev.mit.edu (Postfix) with ESMTPS id 8E5663E623 for ; Fri, 15 Oct 2010 03:01:01 -0400 (EDT) Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103]) by mailhub-auth-1.mit.edu (8.13.8/8.9.2) with ESMTP id o9F711FI026401; Fri, 15 Oct 2010 03:01:01 -0400 Received: from bang.hsd1.ma.comcast.net (c-98-216-239-22.hsd1.ma.comcast.net [98.216.239.22]) (authenticated bits=0) (User authenticated as raeburn@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.6/8.12.4) with ESMTP id o9F70x0d024593 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Fri, 15 Oct 2010 03:01:00 -0400 (EDT) Subject: Re: [krbdev.mit.edu #6803] Config variable for default ccache directory MIME-Version: 1.0 (Apple Message framework v1081) Content-Type: text/plain; charset=us-ascii From: Ken Raeburn In-Reply-To: Date: Fri, 15 Oct 2010 03:00:59 -0400 Content-Transfer-Encoding: quoted-printable Message-ID: <982BA4CB-BB29-41E6-853A-4A155F794B2F@mit.edu> References: To: rt@krbdev.mit.edu X-Mailer: Apple Mail (2.1081) RT-Send-Cc: X-RT-Original-Encoding: us-ascii Content-Length: 677 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