IETF Logo Mail Archive

Re: [kitten] Clarification of gss_add_cred() behavior

Viktor Dukhovni <viktor1dane@dukhovni.org> Thu, 19 March 2015 19:57 UTC

Return-Path: <viktor1dane@dukhovni.org>
X-Original-To: kitten@ietfa.amsl.com
Delivered-To: kitten@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2361E1A1EF3 for <kitten@ietfa.amsl.com>; Thu, 19 Mar 2015 12:57:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level:
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8m5rdC819Uys for <kitten@ietfa.amsl.com>; Thu, 19 Mar 2015 12:57:21 -0700 (PDT)
Received: from mournblade.imrryr.org (mournblade.imrryr.org [38.117.134.19]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A803C1A1A70 for <kitten@ietf.org>; Thu, 19 Mar 2015 12:57:21 -0700 (PDT)
Received: by mournblade.imrryr.org (Postfix, from userid 1034) id 9A3B5283011; Thu, 19 Mar 2015 19:57:20 +0000 (UTC)
Date: Thu, 19 Mar 2015 19:57:20 +0000
From: Viktor Dukhovni <viktor1dane@dukhovni.org>
To: kitten@ietf.org
Message-ID: <20150319195720.GI4309@mournblade.imrryr.org>
References: <20150319025202.GB8099@localhost> <alpine.GSO.1.10.1503191446260.3953@multics.mit.edu> <20150319194002.GG4309@mournblade.imrryr.org> <alpine.GSO.1.10.1503191541510.3953@multics.mit.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <alpine.GSO.1.10.1503191541510.3953@multics.mit.edu>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <http://mailarchive.ietf.org/arch/msg/kitten/XP1m_1fLiXwXdLomlKJOFKC6zLo>
Subject: Re: [kitten] Clarification of gss_add_cred() behavior
X-BeenThere: kitten@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: kitten@ietf.org
List-Id: Common Authentication Technologies - Next Generation <kitten.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/kitten>, <mailto:kitten-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/kitten/>
List-Post: <mailto:kitten@ietf.org>
List-Help: <mailto:kitten-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/kitten>, <mailto:kitten-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Mar 2015 19:57:26 -0000

On Thu, Mar 19, 2015 at 03:50:22PM -0400, Benjamin Kaduk wrote:

> >     2. For this interface to be useful, the initial state one must
> >        be able to start with an empty credential handle and build up
> >        from there.  This presumably is specified via a NULL input
> >        credential, and still the same name for which one wants
> >        creds.
> 
> There is GSS_Acquire_cred to obtain the first credential element.

So I believe that you're saying that gss_add_cred() not intended to
be able to add the *first* credential element.  That is:

    1. Always call gss_acquire_cred() with a singleton mechanism
       set (to get the first mechanism) and desired name.

    2. Then, as appropriate, call gss_add_cred() for any *additional*
       mechanisms.

This makes the API more unpleasant to use, but sounds plausibly
consistent with the text...

-- 
	Viktor.

v2.23.0 | Report a Bug | By Email