IETF Logo Mail Archive

Re: WG Last Call: draft-ietf-sasl-gs2-14

Simon Josefsson <simon@josefsson.org> Wed, 29 July 2009 21:42 UTC

Return-Path: <owner-ietf-sasl@mail.imc.org>
X-Original-To: ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com
Delivered-To: ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6AA0D3A659A for <ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com>; Wed, 29 Jul 2009 14:42:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.572
X-Spam-Level:
X-Spam-Status: No, score=-2.572 tagged_above=-999 required=5 tests=[AWL=0.027, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7kB1uEY4aCj8 for <ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com>; Wed, 29 Jul 2009 14:42:46 -0700 (PDT)
Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2]) by core3.amsl.com (Postfix) with ESMTP id 3726A3A6EF9 for <sasl-archive-Zoh8yoh9@ietf.org>; Wed, 29 Jul 2009 14:42:42 -0700 (PDT)
Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n6TLLRSU098759 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 29 Jul 2009 14:21:27 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n6TLLRxx098758; Wed, 29 Jul 2009 14:21:27 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-sasl@mail.imc.org using -f
Received: from yxa-v.extundo.com (yxa-v.extundo.com [83.241.177.39]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n6TLLECd098747 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf-sasl@imc.org>; Wed, 29 Jul 2009 14:21:26 -0700 (MST) (envelope-from simon@josefsson.org)
Received: from mocca.josefsson.org (c80-216-31-183.bredband.comhem.se [80.216.31.183]) (authenticated bits=0) by yxa-v.extundo.com (8.14.3/8.14.3/Debian-5) with ESMTP id n6TLLBbP000587 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 29 Jul 2009 23:21:13 +0200
From: Simon Josefsson <simon@josefsson.org>
To: Nicolas Williams <Nicolas.Williams@sun.com>
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, ietf-sasl@imc.org
Subject: Re: WG Last Call: draft-ietf-sasl-gs2-14
References: <ldveiskuhya.fsf@cathode-dark-space.mit.edu> <4A6216CC.2050104@isode.com> <87ws5u44xz.fsf@mocca.josefsson.org> <20090729150853.GE1020@Sun.COM> <4A706ADF.5000805@isode.com> <87bpn3wlb5.fsf@mocca.josefsson.org> <20090729205210.GV1020@Sun.COM>
OpenPGP: id=B565716F; url=http://josefsson.org/key.txt
X-Hashcash: 1:22:090729:nicolas.williams@sun.com::Bdse7JcuZ4HsBDdo:4uU
X-Hashcash: 1:22:090729:ietf-sasl@imc.org::h0HrIrtxznDPrpFu:AOw7
X-Hashcash: 1:22:090729:alexey.melnikov@isode.com::ulod3CrSDnTMJUSc:LYL0
Date: Wed, 29 Jul 2009 23:21:11 +0200
In-Reply-To: <20090729205210.GV1020@Sun.COM> (Nicolas Williams's message of "Wed, 29 Jul 2009 15:52:10 -0500")
Message-ID: <87d47jmbi0.fsf@mocca.josefsson.org>
User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.0.96 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Virus-Scanned: clamav-milter 0.95.2 at yxa-v
X-Virus-Status: Clean
Sender: owner-ietf-sasl@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sasl/mail-archive/>
List-ID: <ietf-sasl.imc.org>
List-Unsubscribe: <mailto:ietf-sasl-request@imc.org?body=unsubscribe>

Nicolas Williams <Nicolas.Williams@sun.com> writes:

> Jeff Hutzelman points out that RFC2744 specifically requires that all
> gss_buffer_t outputs be released.  That wouldn't bother me at all here
> (we'd have to say that draft-ietf-sasl-gs2 updates RFC2744), but,
> RFC5587 (draft-ietf-kitten-extended-mech-inquiry, in AUTH48) had a
> chance to do that and didn't, so I'd say that these output buffers
> should be released by the app.

Good catch, I have removed the paragraph.  How memory should be managed
by applications (i.e., they have to be released) then follows directly
from the normative RFC 2744 and GS2 shouldn't say anything about it.
Alexey, I hope this resolves your question.

/Simon

v2.23.0 | Report a Bug | By Email