IETF Logo Mail Archive

Re: [kitten] GSS-API and timeouts

Simon Josefsson <simon@josefsson.org> Wed, 04 April 2012 17:19 UTC

Return-Path: <simon@josefsson.org>
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 A88EC21F8750 for <kitten@ietfa.amsl.com>; Wed, 4 Apr 2012 10:19:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.757
X-Spam-Level:
X-Spam-Status: No, score=-99.757 tagged_above=-999 required=5 tests=[AWL=0.152, BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, HELO_MISMATCH_COM=0.553, HOST_EQ_STATICB=1.372, USER_IN_WHITELIST=-100]
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 4TuxABj+W4T9 for <kitten@ietfa.amsl.com>; Wed, 4 Apr 2012 10:19:44 -0700 (PDT)
Received: from yxa-v.extundo.com (static-213-115-179-173.sme.bredbandsbolaget.se [213.115.179.173]) by ietfa.amsl.com (Postfix) with ESMTP id B08EF21F8595 for <kitten@ietf.org>; Wed, 4 Apr 2012 10:19:43 -0700 (PDT)
Received: from latte.josefsson.org (static-213-115-179-130.sme.bredbandsbolaget.se [213.115.179.130]) (authenticated bits=0) by yxa-v.extundo.com (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id q34HJRf0002821 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 4 Apr 2012 19:19:29 +0200
From: Simon Josefsson <simon@josefsson.org>
To: Simo Sorce <simo@redhat.com>
References: <87obr7lfqc.fsf@latte.josefsson.org> <1333554538.22628.292.camel__5672.95260630107$1333554546$gmane$org@willson.li.ssimo.org>
OpenPGP: id=B565716F; url=http://josefsson.org/key.txt
X-Hashcash: 1:22:120404:simo@redhat.com::Zc+/8p5kNY8qg9Hk:46Ri
X-Hashcash: 1:22:120404:kitten@ietf.org::KdokMlsHcGvgLgOy:+Rbf
Date: Wed, 04 Apr 2012 19:19:27 +0200
In-Reply-To: <1333554538.22628.292.camel__5672.95260630107$1333554546$gmane$org@willson.li.ssimo.org> (Simo Sorce's message of "Wed, 04 Apr 2012 11:48:58 -0400")
Message-ID: <87hawzjty8.fsf@latte.josefsson.org>
User-Agent: Gnus/5.130004 (Ma Gnus v0.4) Emacs/24.0.94 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
X-Virus-Scanned: clamav-milter 0.97.3 at yxa-v
X-Virus-Status: Clean
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 17:19:44 -0000

Simo Sorce <simo@redhat.com> writes:

>> Of course, we could have a new GSS-API interface to enforce a timeout.
>> For example:
>> 
>>      OM_uint32
>>      gss_sec_context_timeout (OM_uint32 *minor_status,
>>                               OM_uint32 timeout);
>> 
>> or something more general, in case there are similar concerns for other
>> functions:
>> 
>> 
>>      OM_uint32
>>      gss_set_timeouts (OM_uint32 *minor_status,
>>                        OM_uint32 sec_context_timeout,
>>                        OM_uint32 micwrap_timeout);
>> 
>> FWIW, in my implementation I'll probably use a 5 minute timeout or
>> something like that.
>
> The problem I see with this kind of calls is that they affect the whole
> process. What if you have 2 libraries with conflicting needs and both
> use gssapi ?

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.

Maybe this is a non-issue.  We'll see how it works in practice.

/Simon

v2.23.0 | Report a Bug | By Email