Re: [kitten] RFC2743 errata 4251

mrex@sap.com (Martin Rex) Tue, 16 December 2014 10:02 UTC

Return-Path: <mrex@sap.com>
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 955361A1A80 for <kitten@ietfa.amsl.com>; Tue, 16 Dec 2014 02:02:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.551
X-Spam-Level:
X-Spam-Status: No, score=-6.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] 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 s0wxBeeDrc6R for <kitten@ietfa.amsl.com>; Tue, 16 Dec 2014 02:02:19 -0800 (PST)
Received: from smtpde02.smtp.sap-ag.de (smtpde02.smtp.sap-ag.de [155.56.68.140]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7A8031A1A4C for <kitten@ietf.org>; Tue, 16 Dec 2014 02:02:19 -0800 (PST)
Received: from mail05.wdf.sap.corp (mail05.sap.corp [194.39.131.55]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtpde02.smtp.sap-ag.de (Postfix) with ESMTPS id 864DA3A0FF; Tue, 16 Dec 2014 11:02:17 +0100 (CET)
Received: from ld9781.wdf.sap.corp (ld9781.wdf.sap.corp [10.21.82.193]) by mail05.wdf.sap.corp (Postfix) with ESMTP id 537B345252; Tue, 16 Dec 2014 11:02:17 +0100 (CET)
Received: by ld9781.wdf.sap.corp (Postfix, from userid 10159) id 4AB701B084; Tue, 16 Dec 2014 11:02:17 +0100 (CET)
In-Reply-To: <20141215230719.GM3241@localhost>
To: Nico Williams <nico@cryptonector.com>
Date: Tue, 16 Dec 2014 11:02:17 +0100
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20141216100217.4AB701B084@ld9781.wdf.sap.corp>
From: mrex@sap.com
Archived-At: http://mailarchive.ietf.org/arch/msg/kitten/NAOJtWhZEIWPf2KFVYcEUkpGgKA
Cc: kitten@ietf.org
Subject: Re: [kitten] RFC2743 errata 4251
X-BeenThere: kitten@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: mrex@sap.com
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: Tue, 16 Dec 2014 10:02:22 -0000

Nico Williams wrote:
> On Mon, Dec 15, 2014 at 10:52:31PM +0100, Martin Rex wrote:
> > Nico Williams wrote:
> > >> (To be clear: saying that applications must eventually call
> > >> GSS_Delete_sec_context() is fine; saying that they should do so
> > >> immediately after a GSS_S_COMPLETE from GSS_Process_context_token() is
> > >> not fine.)
> > > 
> > > GSS-APIv2u1 callers can still call GSS_Unwrap(), GSS_VerifyMIC(), and
> > > GSS_Pseudo_random()[*], and even GSS_Wrap() and GSS_GetMIC() before
> > > calling GSS_Delete_sec_context(), however,
> > 
> > You mean calling GSS_Unwrap(), GSS_VerifyMIC(), GSS_Wrap()
> > GSS_GetMIC() _after_ calling GSS_Delete_sec_context() ?
> 
> No, after calling GSS_Process_context_token().

It seems I was tired last night.

I meant to say:

 You mean calling GSS_Unwrap(), GSS_VerifyMIC(), GSS_Wrap()
 GSS_GetMIC() _after_ calling GSS_Process_sec_context() ?

-Martin