IETF Logo Mail Archive

Re: [kitten] GSS-API and timeouts

Nico Williams <nico@cryptonector.com> Wed, 04 April 2012 22:27 UTC

Return-Path: <nico@cryptonector.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 9358511E80B3 for <kitten@ietfa.amsl.com>; Wed, 4 Apr 2012 15:27:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.776
X-Spam-Level:
X-Spam-Status: No, score=-1.776 tagged_above=-999 required=5 tests=[AWL=0.201, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
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 kZVFosbttUAF for <kitten@ietfa.amsl.com>; Wed, 4 Apr 2012 15:27:15 -0700 (PDT)
Received: from homiemail-a85.g.dreamhost.com (caiajhbdccac.dreamhost.com [208.97.132.202]) by ietfa.amsl.com (Postfix) with ESMTP id D663011E80A2 for <kitten@ietf.org>; Wed, 4 Apr 2012 15:27:15 -0700 (PDT)
Received: from homiemail-a85.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a85.g.dreamhost.com (Postfix) with ESMTP id 94641BC042 for <kitten@ietf.org>; Wed, 4 Apr 2012 15:27:15 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=cryptonector.com; h=mime-version :in-reply-to:references:date:message-id:subject:from:to:cc :content-type:content-transfer-encoding; q=dns; s= cryptonector.com; b=QFB4GTNS5yPaaLGpFfy1phbm0obENdzRJIN+WbgP4lUh rek7U+VjaWakDLJiCkL7atbuWEPwAzgteICqSKs3PAjoYLFphUUMGMQOZ1mWMpe5 RTC7XM3pK47YdYOXjvLyKxTsnVV69YpY5UffwRnqTL3wn8D6bbb2bEvZiBkXkSg=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h= mime-version:in-reply-to:references:date:message-id:subject:from :to:cc:content-type:content-transfer-encoding; s= cryptonector.com; bh=YYno1Gab+rs1wQSE6jG1MOoqYXM=; b=DRU35kk3kCo ZuHNRXkuNsNFYOr0RhfENCZti4ntAKSLvv2Vivl0yj+TZJLTIqzBCm0HybIsWBFK X4shmAJRH20OqAh0dwTZgBNL2GtAGKravcXOJjGQklYq250qap7yQUuwOTJb8Akv JxsXde6gxK066+5kQ+xW3y1+1hSU3hfo=
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a85.g.dreamhost.com (Postfix) with ESMTPSA id 7A3F6BC040 for <kitten@ietf.org>; Wed, 4 Apr 2012 15:27:15 -0700 (PDT)
Received: by pbbrq13 with SMTP id rq13so743731pbb.31 for <kitten@ietf.org>; Wed, 04 Apr 2012 15:27:15 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.68.132.99 with SMTP id ot3mr1261997pbb.160.1333578435023; Wed, 04 Apr 2012 15:27:15 -0700 (PDT)
Received: by 10.68.28.6 with HTTP; Wed, 4 Apr 2012 15:27:14 -0700 (PDT)
In-Reply-To: <87y5qbnnsk.fsf@windlord.stanford.edu>
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>
Date: Wed, 04 Apr 2012 17:27:14 -0500
Message-ID: <CAK3OfOhOZcbP=WyDt+_vFHVKbFxaXrwET=FX-xWF2Gnv9fR6bQ@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: Russ Allbery <rra@stanford.edu>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
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:27:16 -0000

On Wed, Apr 4, 2012 at 5:18 PM, Russ Allbery <rra@stanford.edu> wrote:
> Simon Josefsson <simon@josefsson.org> writes:
> 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.

Maybe I should finish up my pgss work and write an I-D.  The API is
trivial, the changes to the mechs are trivial, the changes to the
mechglue are rote (but extensive, mostly in the form of a simple
addition to the preamble of most GSS functions).

v2.23.0 | Report a Bug | By Email