IETF Logo Mail Archive

Re: [kitten] Windows Intent to revive and implement IAKerb draft-ietf-kitten-iakerb-03

Greg Hudson <ghudson@mit.edu> Fri, 17 February 2023 05:14 UTC

Return-Path: <ghudson@mit.edu>
X-Original-To: kitten@ietfa.amsl.com
Delivered-To: kitten@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA47CC16952F for <kitten@ietfa.amsl.com>; Thu, 16 Feb 2023 21:14:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.398
X-Spam-Level:
X-Spam-Status: No, score=-4.398 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mit.edu
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mPiR_I6Qa5sF for <kitten@ietfa.amsl.com>; Thu, 16 Feb 2023 21:14:09 -0800 (PST)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C6039C153CA8 for <kitten@ietf.org>; Thu, 16 Feb 2023 21:14:08 -0800 (PST)
Received: from [18.30.134.98] ([18.30.134.98]) (authenticated bits=0) (User authenticated as ghudson@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 31H5E1ut030484 (version=TLSv1/SSLv3 cipher=AES128-GCM-SHA256 bits=128 verify=NOT); Fri, 17 Feb 2023 00:14:05 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mit.edu; s=outgoing; t=1676610846; bh=uuPOH7ucmJNWqvpFCFFTPiUNgIJ6GgtiIq1214UyJ8w=; h=Date:Subject:To:References:From:In-Reply-To; b=L6SdsE/oe+p2FHkjTuOZPbMqxhI5ocy57MbQILgsejZSqhohtfKOKcw5U7gmbybsV fywNhc3Dbwrzo1x0nkoVOp/8V3OyDVRuyRdYjUHicLyUIrSDnHhnHEWPQ6a2srNL2U us6oimunD9Pnl7llAY+WYU1GvHRtCWzSo99SP2Qj72VukbdR6/kWSoYiBaAIlO4Goh p5g+tOER23/MolMcRsi1yfeTWhrIoOtTOIYlZlyHHHVXS/f/SepjON765YmKu+MXhM AbA0Cluq+CipAFT0YIJDTTLNPV0seY2Qn5ZzUYlFIp/qzf2sYWaDxPwm4EQT+4voml 1xK0BV219LMwA==
Message-ID: <a6f4ebf9-737c-95b5-ccbf-6a3bc3de4e54@mit.edu>
Date: Fri, 17 Feb 2023 00:14:00 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.4.2
Content-Language: en-US
To: "Steve Syfuhs (AP)" <Steve.Syfuhs=40microsoft.com@dmarc.ietf.org>, "kitten@ietf.org" <kitten@ietf.org>
References: <MW4PR21MB1970A9D254B943A1763C55FF9CA09@MW4PR21MB1970.namprd21.prod.outlook.com>
From: Greg Hudson <ghudson@mit.edu>
In-Reply-To: <MW4PR21MB1970A9D254B943A1763C55FF9CA09@MW4PR21MB1970.namprd21.prod.outlook.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/kitten/Ux0XyH9ziKA5HE69dulXI6gPUbw>
Subject: Re: [kitten] Windows Intent to revive and implement IAKerb draft-ietf-kitten-iakerb-03
X-BeenThere: kitten@ietf.org
X-Mailman-Version: 2.1.39
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: <https://mailarchive.ietf.org/arch/browse/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: Fri, 17 Feb 2023 05:14:12 -0000

On 2/16/23 18:57, Steve Syfuhs (AP) wrote:
> What is the state of the MIT implementation?

It still implements the older draft, so the text in appendix A is still 
necessary to interoperate with it.  We have not as yet implemented 
appendix A in MIT krb5.

I haven't heard of anyone using MIT krb5's IAKERB implementation 
intentionally, and we made it somewhat harder to do so in release 1.14 
without complaint, so there may be limited current value in preserving 
interoperability with it.

Here's a good starting link to old discussion of the interop issue:

https://mailarchive.ietf.org/arch/msg/kitten/3c5Jvq9Hcu3SxNZX6OV-Q6CaypE/

See the seventh (of nine) message in the thread where I proposed what 
became the text of appendix A in the draft.

v2.23.0 | Report a Bug | By Email