IETF Logo Mail Archive

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

Nicolas Williams <Nicolas.Williams@sun.com> Wed, 29 July 2009 22:08 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 CD42E3A6BEF for <ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com>; Wed, 29 Jul 2009 15:08:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.778
X-Spam-Level:
X-Spam-Status: No, score=-5.778 tagged_above=-999 required=5 tests=[AWL=0.268, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-4]
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 k6ODGoDxTIdl for <ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com>; Wed, 29 Jul 2009 15:08:03 -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 AEBA83A6AD2 for <sasl-archive-Zoh8yoh9@ietf.org>; Wed, 29 Jul 2009 15:08:02 -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 n6TLngPC000605 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 29 Jul 2009 14:49:42 -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 n6TLngxd000604; Wed, 29 Jul 2009 14:49:42 -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 brmea-mail-1.sun.com (brmea-mail-1.Sun.COM [192.18.98.31]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n6TLnVR2000587 for <ietf-sasl@imc.org>; Wed, 29 Jul 2009 14:49:41 -0700 (MST) (envelope-from Nicolas.Williams@sun.com)
Received: from dm-central-01.central.sun.com ([129.147.62.4]) by brmea-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n6TLnULw029090 for <ietf-sasl@imc.org>; Wed, 29 Jul 2009 21:49:30 GMT
Received: from binky.Central.Sun.COM (binky.Central.Sun.COM [129.153.128.104]) by dm-central-01.central.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n6TLnU4t036668 for <ietf-sasl@imc.org>; Wed, 29 Jul 2009 15:49:30 -0600 (MDT)
Received: from binky.Central.Sun.COM (localhost [127.0.0.1]) by binky.Central.Sun.COM (8.14.3+Sun/8.14.3) with ESMTP id n6TLd3TF008618; Wed, 29 Jul 2009 16:39:03 -0500 (CDT)
Received: (from nw141292@localhost) by binky.Central.Sun.COM (8.14.3+Sun/8.14.3/Submit) id n6TLd3qA008617; Wed, 29 Jul 2009 16:39:03 -0500 (CDT)
X-Authentication-Warning: binky.Central.Sun.COM: nw141292 set sender to Nicolas.Williams@sun.com using -f
Date: Wed, 29 Jul 2009 16:39:03 -0500
From: Nicolas Williams <Nicolas.Williams@sun.com>
To: Simon Josefsson <simon@josefsson.org>
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, ietf-sasl@imc.org
Subject: Re: WG Last Call: draft-ietf-sasl-gs2-14
Message-ID: <20090729213903.GX1020@Sun.COM>
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> <87d47jmbi0.fsf@mocca.josefsson.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <87d47jmbi0.fsf@mocca.josefsson.org>
User-Agent: Mutt/1.5.7i
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>

On Wed, Jul 29, 2009 at 11:21:11PM +0200, Simon Josefsson wrote:
> 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.

It's useful for GS2 to remind the reader of the application's
responsibility to release these buffers (RFC5587 will do just that).

v2.23.0 | Report a Bug | By Email