Re: [kitten] Use of GSS_Get_name_attribute() to obtain further attributes

Nico Williams <> Wed, 15 April 2015 19:59 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 55C3A1A89E1 for <>; Wed, 15 Apr 2015 12:59:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -0.266
X-Spam-Status: No, score=-0.266 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id mjc7G4sLxnMG for <>; Wed, 15 Apr 2015 12:59:31 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id B1B3E1A89D3 for <>; Wed, 15 Apr 2015 12:59:31 -0700 (PDT)
Received: from (localhost []) by (Postfix) with ESMTP id 940AB2004F31D; Wed, 15 Apr 2015 12:59:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed;; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to;; bh=uepPJWtW+pjxHj 5rnlyVwltFR3o=; b=pWF6D3GblmwwFfLwmiI9yDig6v0+o3WaS8N7DBC3PAV28H EW/pR4XlJkZoPZFC8YfBVcBbH5jp1VL/rxVUaqMzlj2Q56vxAC7GXvHlfLtrM/S3 vK/LGu7Q2FX6BFyMxkXQXHqZCrpFXaZx4G6vL4XsNNlqk1VwaFXuL2cX42etY=
Received: from localhost ( []) (Authenticated sender: by (Postfix) with ESMTPA id CCA492004F322; Wed, 15 Apr 2015 12:59:30 -0700 (PDT)
Date: Wed, 15 Apr 2015 14:59:29 -0500
From: Nico Williams <>
To: Benjamin Kaduk <>
Message-ID: <20150415195928.GD29890@localhost>
References: <> <> <>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <>
Cc:, Simo Sorce <>
Subject: Re: [kitten] Use of GSS_Get_name_attribute() to obtain further attributes
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Common Authentication Technologies - Next Generation <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 15 Apr 2015 19:59:32 -0000

On Mon, Apr 13, 2015 at 11:43:59AM -0400, Benjamin Kaduk wrote:
> I do not think I am opposed to (1) (i.e., letting GSS_Get_name_attribute()
> block on network interaction), but if we proceed down that route, I think
> we should file an erratum against 6880 to that effect.

I do not think that RFC6680 says or implies that only those attributes
listed by GSS_Inquire_name() may be gotten with
GSS_Get_name_attribute(), so to start with, we don't need to change
anything about RFC6680 w.r.t. that.

As for what blocking/non-blocking behavior can be expected, I'd say:

a) GSS_Inquire_name() can never "block",
b) GSS_Get_name_attribute() can, and whether it can should depend on the
   attribute being gotten, and preferably this is described by the
   attribute's documentation.

For the latter, see draft-williams-kitten-generic-naming-attributes-02,
which describes a generic attribute prefix by which the application can
request non-blocking behavior (which can fail if whatever data is not