IETF Logo Mail Archive

[kitten] Request for summary of issues with existing AES-CTS with new SHA2

Michiko Short <michikos@microsoft.com> Tue, 29 October 2013 21:20 UTC

Return-Path: <michikos@microsoft.com>
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 99B4711E81C9 for <kitten@ietfa.amsl.com>; Tue, 29 Oct 2013 14:20:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level:
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dwfrc9pLbnzB for <kitten@ietfa.amsl.com>; Tue, 29 Oct 2013 14:19:54 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0239.outbound.protection.outlook.com [207.46.163.239]) by ietfa.amsl.com (Postfix) with ESMTP id A72C021E8087 for <kitten@ietf.org>; Tue, 29 Oct 2013 14:19:53 -0700 (PDT)
Received: from BLUPR03CA033.namprd03.prod.outlook.com (10.141.30.26) by BLUPR03MB066.namprd03.prod.outlook.com (10.255.209.154) with Microsoft SMTP Server (TLS) id 15.0.785.10; Tue, 29 Oct 2013 21:19:51 +0000
Received: from BY2FFO11FD006.protection.gbl (2a01:111:f400:7c0c::187) by BLUPR03CA033.outlook.office365.com (2a01:111:e400:879::26) with Microsoft SMTP Server (TLS) id 15.0.785.10 via Frontend Transport; Tue, 29 Oct 2013 21:19:52 +0000
Received: from mail.microsoft.com (131.107.125.37) by BY2FFO11FD006.mail.protection.outlook.com (10.1.14.127) with Microsoft SMTP Server (TLS) id 15.0.805.12 via Frontend Transport; Tue, 29 Oct 2013 21:19:51 +0000
Received: from TK5EX14MBXC283.redmond.corp.microsoft.com ([169.254.2.109]) by TK5EX14HUBC102.redmond.corp.microsoft.com ([157.54.7.154]) with mapi id 14.03.0158.002; Tue, 29 Oct 2013 21:18:47 +0000
From: Michiko Short <michikos@microsoft.com>
To: "kitten@ietf.org" <kitten@ietf.org>
Thread-Topic: Request for summary of issues with existing AES-CTS with new SHA2
Thread-Index: Ac7U7AyPw5IckBFDS8WKQUaiQqCs1g==
Date: Tue, 29 Oct 2013 21:18:47 +0000
Message-ID: <5674376E76F88641AD3748A64F0996971AE76A8B@TK5EX14MBXC283.redmond.corp.microsoft.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [157.54.51.71]
Content-Type: multipart/alternative; boundary="_000_5674376E76F88641AD3748A64F0996971AE76A8BTK5EX14MBXC283r_"
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(164054003)(189002)(199002)(49866001)(47736001)(63696002)(83322001)(83072001)(66066001)(54356001)(74502001)(47446002)(80022001)(15202345003)(65816001)(47976001)(50986001)(512954002)(55846006)(15975445006)(19580395003)(81816001)(84326002)(74706001)(44976005)(87266001)(46102001)(74366001)(85306002)(51856001)(53806001)(20776003)(4396001)(71186001)(76482001)(81686001)(54316002)(77096001)(6806004)(69226001)(56776001)(74876001)(31966008)(79102001)(19300405004)(80976001)(76176001)(74662001)(81542001)(33656001)(76796001)(59766001)(76786001)(77982001)(56816003)(16236675002)(81342001); DIR:OUT; SFP:; SCL:1; SRVR:BLUPR03MB066; H:mail.microsoft.com; CLIP:131.107.125.37; FPR:; RD:InfoDomainNonexistent; MX:1; A:1; LANG:en;
X-O365ENT-EOP-Header: Message processed by - O365_ENT: Allow from ranges (Engineering ONLY)
X-Forefront-PRVS: 0014E2CF50
X-OriginatorOrg: DuplicateDomain-a84fc36a-4ed7-4e57-ab1c-3e967bcbad48.microsoft.com
Cc: Anoosh Saboori <ansaboor@microsoft.com>
Subject: [kitten] Request for summary of issues with existing AES-CTS with new SHA2
X-BeenThere: kitten@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 29 Oct 2013 21:20:00 -0000

Can someone summarize what the issues blocking using the existing AES-CTS with SHA2? We have had several discussions over the past months discussing various aspects, but it is unclear to me what the blockers were that makes what we all implemented for SHA1 not feasible for SHA2.


Thanks,
Michiko Short | Program Manager | Windows Security & Identity

v2.46.0 | Report a Bug | By Email | System Status