Received: from biscayne-one-station.mit.edu (BISCAYNE-ONE-STATION.MIT.EDU [18.7.7.80]) by krbdev.mit.edu (8.9.3p2) with ESMTP id PAA08792; Wed, 8 Jun 2005 15:03:35 -0400 (EDT) Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103]) by biscayne-one-station.mit.edu (8.12.4/8.9.2) with ESMTP id j58J3YKH018979; Wed, 8 Jun 2005 15:03:34 -0400 (EDT) Received: from [18.18.1.76] (KEN-WIRELESS.MIT.EDU [18.18.1.76]) (authenticated bits=0) (User authenticated as raeburn@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.1/8.12.4) with ESMTP id j58J3O6c003930 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT); Wed, 8 Jun 2005 15:03:25 -0400 (EDT) In-Reply-To: References: MIME-Version: 1.0 (Apple Message framework v622) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <180d9ac9a4c322f5c2b2bd2cd99f1362@mit.edu> Content-Transfer-Encoding: 7bit From: Ken Raeburn Subject: Re: [krbdev.mit.edu #3091] add krb5_cc_new_unique() Date: Wed, 8 Jun 2005 15:03:08 -0400 To: rt@krbdev.mit.edu X-Mailer: Apple Mail (2.622) X-Spam-Score: -2.099 X-Spam-Flag: NO X-Scanned-BY: MIMEDefang 2.42 RT-Send-Cc: X-RT-Original-Encoding: us-ascii Content-Length: 827 On Jun 8, 2005, at 14:07, Jeffrey Altman via RT wrote: > /* > * Generates a new unique ccache of `type` in `id'. The supplied > * `hint' (that can be NULL) is a string that the credential cache > * type can use to base the name of the credential on, this is to make > * its easier for the user to differentiate the credentials. > * > * Returns 0 or an error code. > */ > > krb5_error_code > krb5_cc_new_unique(krb5_context context, const char *type, > const char *hint, krb5_ccache *id) And how is this different from krb5_cc_gen_new, which should also create a unique credentials cache? Oh, yes, that one requires a ccache object as input, and this one takes a type name. The name should should reflect that. The words "new unique" could apply to either interface. How about krb5_cc_gen_by_type(_name)?