Re: [kitten] New Version Notification for draft-kaduk-kitten-gss-loop-01.txt (fwd)

Jeffrey Hutzelman <jhutz@cmu.edu> Thu, 21 November 2013 15:45 UTC

Return-Path: <jhutz@cmu.edu>
X-Original-To: kitten@ietfa.amsl.com
Delivered-To: kitten@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF46B1AE217 for <kitten@ietfa.amsl.com>; Thu, 21 Nov 2013 07:45:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.725
X-Spam-Level:
X-Spam-Status: No, score=-4.725 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.525] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4286j951BtoQ for <kitten@ietfa.amsl.com>; Thu, 21 Nov 2013 07:45:39 -0800 (PST)
Received: from smtp03.srv.cs.cmu.edu (SMTP03.SRV.CS.CMU.EDU [128.2.217.198]) by ietfa.amsl.com (Postfix) with ESMTP id 0DEE21AE168 for <kitten@ietf.org>; Thu, 21 Nov 2013 07:45:38 -0800 (PST)
Received: from [192.168.202.142] (pool-108-39-146-104.pitbpa.fios.verizon.net [108.39.146.104]) (authenticated bits=0) by smtp03.srv.cs.cmu.edu (8.13.6/8.13.6) with ESMTP id rALFjTaF025677 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 21 Nov 2013 10:45:30 -0500 (EST)
Message-ID: <1385048728.6315.4.camel@destiny.pc.cs.cmu.edu>
From: Jeffrey Hutzelman <jhutz@cmu.edu>
To: Greg Hudson <ghudson@MIT.EDU>
Date: Thu, 21 Nov 2013 10:45:28 -0500
In-Reply-To: <17813_1384989489_rAKNI8L6018086_528D431C.5020803@mit.edu>
References: <alpine.GSO.1.10.1311201407400.23560@multics.mit.edu> <alpine.GSO.1.10.1311201733070.23560@multics.mit.edu> <17813_1384989489_rAKNI8L6018086_528D431C.5020803@mit.edu>
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.8.4-0ubuntu1
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
X-Scanned-By: mimedefang-cmuscs on 128.2.217.198
Cc: kitten@ietf.org, jhutz@cmu.edu
Subject: Re: [kitten] New Version Notification for draft-kaduk-kitten-gss-loop-01.txt (fwd)
X-BeenThere: kitten@ietf.org
X-Mailman-Version: 2.1.15
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: Thu, 21 Nov 2013 15:45:41 -0000

On Wed, 2013-11-20 at 18:17 -0500, Greg Hudson wrote:
> On 11/20/2013 05:45 PM, Benjamin Kaduk wrote:
> > We discussed whether (either at the abstract level or the C bindings) it
> > is guaranteed to be safe to call gss_release_buffer() twice on the same
> > buffer.
> 
> I think that unfortunately it is not safe per the spec, although it is
> probably safe in every GSSAPI implementation.
> 
> > The send_token()/receive_token() routines are not very good examples. 
> > It is probably better to rewrite them to use sendmsg/recvmsg with
> > socketpair, which also eliminates the need to add framing with the token
> > length.
> 
> I think the RFC should only include the do_initiator() and do_acceptor()
> functions.  The sample code does not need to compile and run, only
> demonstrate how the API should be used and be a reasonable starting
> point for cut and paste.

Agree.

-- Jeff