Re: [kitten] GSS-API and timeouts

Luke Howard <lukeh@padl.com> Wed, 04 April 2012 22:33 UTC

Return-Path: <lukeh@padl.com>
X-Original-To: kitten@ietfa.amsl.com
Delivered-To: kitten@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A687F11E811E for <kitten@ietfa.amsl.com>; Wed, 4 Apr 2012 15:33:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YHGoo8W7uUO6 for <kitten@ietfa.amsl.com>; Wed, 4 Apr 2012 15:33:51 -0700 (PDT)
Received: from us.padl.com (us.padl.com [216.154.215.154]) by ietfa.amsl.com (Postfix) with ESMTP id 183DF11E812A for <kitten@ietf.org>; Wed, 4 Apr 2012 15:33:51 -0700 (PDT)
Received: by us.padl.com with ESMTP id q34MXlKC011796; Wed, 4 Apr 2012 18:33:49 -0400
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset="us-ascii"
From: Luke Howard <lukeh@padl.com>
In-Reply-To: <87y5qbnnsk.fsf@windlord.stanford.edu>
Date: Thu, 05 Apr 2012 08:33:49 +1000
Content-Transfer-Encoding: quoted-printable
Message-Id: <4C60BAE9-E039-438E-B686-400753A0AFD7@padl.com>
References: <87obr7lfqc.fsf@latte.josefsson.org> <1333554538.22628.292.camel__5672.95260630107$1333554546$gmane$org@willson.li.ssimo.org> <87hawzjty8.fsf@latte.josefsson.org> <87y5qbnnsk.fsf@windlord.stanford.edu>
To: Russ Allbery <rra@stanford.edu>
X-Mailer: Apple Mail (2.1257)
X-SMTP-Vilter-Version: 1.3.6
X-Spamd-Symbols: AWL,BAYES_00,USER_IN_WHITELIST
X-SMTP-Vilter-Spam-Backend: spamd
X-Spam-Threshold: 5.0
X-Spam-Probability: -20.5
Cc: kitten@ietf.org
Subject: Re: [kitten] GSS-API and timeouts
X-BeenThere: kitten@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
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: Wed, 04 Apr 2012 22:33:55 -0000

On 05/04/2012, at 8:18 AM, Russ Allbery wrote:

> Simon Josefsson <simon@josefsson.org> writes:
> 
>> Yeah, it is not optimal.  We could make it take a 'gss_ctx_id_t'
>> parameter so the timeout is just for a particular context, but then
>> there is no way to specify a timeout for the initial call that generate
>> the gss_ctx_id_t.
> 
> The lack of ability to set options on the initial call has been a problem
> for a long time.  In a Kerberos context, it currently means that one has
> to set a per-thread global for the ticket cache to use, for example,
> rather than attaching some state to a specific GSS-API interaction.


The non-standard extension gss_set_sec_context_option() can create a context handle which can be then passed to the first gss_init_sec_context().

-- Luke