[sasl] GS2 fixes
Simon Josefsson <simon@josefsson.org> Tue, 02 March 2010 16:16 UTC
Return-Path: <simon@josefsson.org>
X-Original-To: sasl@core3.amsl.com
Delivered-To: sasl@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C6CA128C12C for <sasl@core3.amsl.com>; Tue, 2 Mar 2010 08:16:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.716
X-Spam-Level:
X-Spam-Status: No, score=-2.716 tagged_above=-999 required=5 tests=[AWL=-0.117, 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 R1eYF+rRIdTh for <sasl@core3.amsl.com>; Tue, 2 Mar 2010 08:16:38 -0800 (PST)
Received: from yxa-v.extundo.com (yxa-v.extundo.com [83.241.177.39]) by core3.amsl.com (Postfix) with ESMTP id D6F2728C141 for <sasl@ietf.org>; Tue, 2 Mar 2010 08:16:35 -0800 (PST)
Received: from mocca (c80-216-24-99.bredband.comhem.se [80.216.24.99]) (authenticated bits=0) by yxa-v.extundo.com (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id o22GGNCw029796 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for <sasl@ietf.org>; Tue, 2 Mar 2010 17:16:29 +0100
X-Hashcash: 1:22:100302:sasl@ietf.org::aU+CFC6v0hfThb62:QoEH
From: Simon Josefsson <simon@josefsson.org>
To: sasl@ietf.org
OpenPGP: id=B565716F; url=http://josefsson.org/key.txt
Date: Tue, 02 Mar 2010 17:16:23 +0100
Message-ID: <87ocj6r960.fsf@mocca.josefsson.org>
User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.1 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Virus-Scanned: clamav-milter 0.95.3 at yxa-v
X-Virus-Status: Clean
Subject: [sasl] GS2 fixes
X-BeenThere: sasl@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SASL Working Group <sasl.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sasl>, <mailto:sasl-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sasl>
List-Post: <mailto:sasl@ietf.org>
List-Help: <mailto:sasl-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sasl>, <mailto:sasl-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Mar 2010 16:16:38 -0000
GS2 is in AUTH48 so I took some time to revise my implementation and noticed that the GSS-API interface descriptions were underspecified. I intend to send the following request to the RFC editor unless there are any objections within a few days. The text is mostly copy'n'paste from similar descriptions in RFC 2743/2744. /Simon OLD (section 10.1): minor_status Integer, modify Mechanism specific status code. NEW: minor_status Integer, modify Mechanism specific status code. desired_mech OID, read Identifies the GSS-API mechanism to query. sasl_mech_name buffer, character-string, modify, optional Buffer to receive SASL mechanism name. The application must free storage associated with this name after use with a call to gss_release_buffer(). mech_name buffer, character-string, modify, optional Buffer to receive human readable mechanism name. The application must free storage associated with this name after use with a call to gss_release_buffer(). mech_description buffer, character-string, modify, optional Buffer to receive description of mechanism. The application must free storage associated with this name after use with a call to gss_release_buffer(). OLD (section 11): o mech_type OBJECT IDENTIFIER -- must be explicit mechanism, and not "default" specifier NEW: o mech_type OBJECT IDENTIFIER -- must be explicit mechanism, and not "default" specifier. Caller should treat as read-only and should not attempt to release. OLD (section 11.1): minor_status Integer, modify Mechanism specific status code. NEW: minor_status Integer, modify Mechanism specific status code. sasl_mech_name buffer, character-string, read Buffer with SASL mechanism name. mech_type OID, modify, optional Actual mechanism used. The OID returned via this parameter will be a pointer to static storage that should be treated as read-only; In particular the application should not attempt to free it. Specify NULL if not required. OLD (section 11.1): GSS_S_BAD_MECH The desired_mech OID is unsupported NEW: GSS_S_BAD_MECH There is no GSS-API mechanism known as sasl_mech_name
- [sasl] GS2 fixes Simon Josefsson