RE: aes128gcm: is the 1st example wrong?
"Manger, James" <James.H.Manger@team.telstra.com> Thu, 16 February 2017 01:14 UTC
Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=lists.ie@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A3946129C30 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 15 Feb 2017 17:14:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level:
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=teamtelstra.onmicrosoft.com
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 7S5qqUt2bx2t for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 15 Feb 2017 17:14:36 -0800 (PST)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3DA47129B91 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Wed, 15 Feb 2017 17:14:36 -0800 (PST)
Received: from lists by frink.w3.org with local (Exim 4.80) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1ceAcc-0001Ix-0w for ietf-http-wg-dist@listhub.w3.org; Thu, 16 Feb 2017 01:12:34 +0000
Resent-Date: Thu, 16 Feb 2017 01:12:34 +0000
Resent-Message-Id: <E1ceAcc-0001Ix-0w@frink.w3.org>
Received: from titan.w3.org ([128.30.52.76]) by frink.w3.org with esmtps (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <James.H.Manger@team.telstra.com>) id 1ceAcX-0001Hi-1P for ietf-http-wg@listhub.w3.org; Thu, 16 Feb 2017 01:12:29 +0000
Received: from ipxcno.tcif.telstra.com.au ([203.35.82.208]) by titan.w3.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.84_2) (envelope-from <James.H.Manger@team.telstra.com>) id 1ceAcL-0003sJ-L6 for ietf-http-wg@w3.org; Thu, 16 Feb 2017 01:12:22 +0000
X-IronPort-AV: E=Sophos;i="5.35,167,1483966800"; d="scan'208";a="23494507"
Received: from unknown (HELO ipcbni.tcif.telstra.com.au) ([10.97.216.204]) by ipocni.tcif.telstra.com.au with ESMTP; 16 Feb 2017 12:11:45 +1100
X-IronPort-AV: E=McAfee;i="5800,7501,8440"; a="303930406"
Received: from wsmsg3702.srv.dir.telstra.com ([172.49.40.170]) by ipcbni.tcif.telstra.com.au with ESMTP; 16 Feb 2017 12:11:45 +1100
Received: from wsapp5870.srv.dir.telstra.com (10.75.139.12) by wsmsg3702.srv.dir.telstra.com (172.49.40.170) with Microsoft SMTP Server (TLS) id 8.3.485.1; Thu, 16 Feb 2017 12:11:45 +1100
Received: from wsapp5585.srv.dir.telstra.com (10.75.3.67) by wsapp5870.srv.dir.telstra.com (10.75.139.12) with Microsoft SMTP Server (TLS) id 15.0.1236.3; Thu, 16 Feb 2017 12:11:44 +1100
Received: from AUS01-ME1-obe.outbound.protection.outlook.com (10.172.101.125) by wsapp5585.srv.dir.telstra.com (10.75.3.67) with Microsoft SMTP Server (TLS) id 15.0.1236.3 via Frontend Transport; Thu, 16 Feb 2017 12:11:43 +1100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=teamtelstra.onmicrosoft.com; s=selector1-team-telstra-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=nbbtSbnZBZ0vftmmuiqF7JwqcYjg0vmpBbPkWtIjKNM=; b=GXJV2eozG6RkcHlvj2YEkrX91ksiy3ynxOqOFva7FZeKtxoX9zANiCyyhBNeKDlbtlA/6D0gYC623n1UOll6PaAcYawsK8f1TqJer1lKyPeLXgzksJPBI9/tdTqPGlVrCvNFhWpvXHFPmLTRf+Edwm9D39fuYXDcreqFE9plYXo=
Received: from SYXPR01MB1615.ausprd01.prod.outlook.com (10.175.209.15) by SYXPR01MB1614.ausprd01.prod.outlook.com (10.175.209.14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.888.16; Thu, 16 Feb 2017 01:11:43 +0000
Received: from SYXPR01MB1615.ausprd01.prod.outlook.com ([10.175.209.15]) by SYXPR01MB1615.ausprd01.prod.outlook.com ([10.175.209.15]) with mapi id 15.01.0888.030; Thu, 16 Feb 2017 01:11:43 +0000
From: "Manger, James" <James.H.Manger@team.telstra.com>
To: Daurnimator <quae@daurnimator.com>
CC: "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
Thread-Topic: aes128gcm: is the 1st example wrong?
Thread-Index: AdJwaRiaLg2sNqShRRuJIHKdUn2T6gABvL4ABT4xjoAAB90lgAAAE/2gABH+04AAAYDlAACGmvAAAAAO11A=
Date: Thu, 16 Feb 2017 01:11:43 +0000
Message-ID: <SYXPR01MB16157B1A0656DE1BDF8F7727E55A0@SYXPR01MB1615.ausprd01.prod.outlook.com>
References: <SYXPR01MB1615D5823473E6A9B5F0C80DE57C0@SYXPR01MB1615.ausprd01.prod.outlook.com> <CABkgnnWE38wbhKfp+5nF1hfn7qH4-6Uk4QMGBKgGL6-f_em_KA@mail.gmail.com> <1459eb07-f8cb-ff90-6101-be05f80c76aa@gmx.de> <CABkgnnVVc3OvJh1ukTuaFmrbOLgEiVWSqfKGP74ct=TKxpZxTg@mail.gmail.com> <SYXPR01MB1615A9EA6825C721A3ACCEA9E5460@SYXPR01MB1615.ausprd01.prod.outlook.com> <daa227a4-e2b7-f9cc-7468-b1f2ebfc69c1@gmx.de> <CABkgnnUxtcNnrs=O3bVNbuMnLuX6HpHNG-bkhDQn7ZZmzvuiiA@mail.gmail.com> <CAEnbY+dfBAqAMfm5Y0gMYCSPT4mEfR11C4tLdyOSYsf6R1865g@mail.gmail.com>
In-Reply-To: <CAEnbY+dfBAqAMfm5Y0gMYCSPT4mEfR11C4tLdyOSYsf6R1865g@mail.gmail.com>
Accept-Language: en-AU, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=James.H.Manger@team.telstra.com;
x-originating-ip: [203.35.9.18]
x-ms-office365-filtering-correlation-id: 645477b8-056b-4ee1-75ad-08d45608c53f
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:(22001);SRVR:SYXPR01MB1614;
x-microsoft-exchange-diagnostics: 1; SYXPR01MB1614; 7:dLVw8KMhPORZztwWOjto8nDvBckY/6nhskhfZk7N/QPUlpKqh+SU03gJd5sC7Ptd06ci1c1ZOh08phEj4TRmjmI9Qnct/kmvFIMpC56/YiSJn1EOllJJ8kU0rU8YfVqAvDzxC5mGRjcqgUkTxjxLRikGm4JeXIYoSzPeT7FF60Z5xu60LuTONpBc/Y3OZiXwz1ElB40ebHAoyDzUp4YZpC51QTnz6DubFZ/fnCzDRlLXvg3RwFMBtLVNyPiEqhrRGJoLBbfEA70OxlDBYERjXs3/7KsN+mgXtWrQdY2MNmr3XO9L1j246PuFjk8TpPEGxfXEc/4S4h48TYOJS3J3aQ==
x-microsoft-antispam-prvs: <SYXPR01MB16149B4BDF458BD285D8EC2AE55A0@SYXPR01MB1614.ausprd01.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(26323138287068)(272811157607776)(67441168502697);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040375)(2401047)(8121501046)(5005006)(3002001)(10201501046)(6041248)(20161123555025)(20161123558025)(20161123564025)(20161123562025)(20161123560025)(6072148); SRVR:SYXPR01MB1614; BCL:0; PCL:0; RULEID:; SRVR:SYXPR01MB1614;
x-forefront-prvs: 0220D4B98D
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(7916002)(39450400003)(24454002)(377454003)(13464003)(199003)(189002)(66066001)(189998001)(7696004)(6916009)(92566002)(101416001)(93886004)(5660300001)(33656002)(97736004)(8676002)(2900100001)(76176999)(81156014)(86362001)(54356999)(3660700001)(53936002)(42882006)(2950100002)(68736007)(50986999)(106356001)(229853002)(6506006)(9686003)(99286003)(55016002)(25786008)(77096006)(305945005)(105586002)(74316002)(6116002)(81166006)(53546003)(6436002)(8936002)(6246003)(3280700002)(102836003)(3846002)(2906002)(110136004)(4326007)(389900002)(122556002)(7736002)(38730400002); DIR:OUT; SFP:1102; SCL:1; SRVR:SYXPR01MB1614; H:SYXPR01MB1615.ausprd01.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:0; MX:1; LANG:en;
received-spf: None (protection.outlook.com: team.telstra.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 16 Feb 2017 01:11:43.4189 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 49dfc6a3-5fb7-49f4-adea-c54e725bb854
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SYXPR01MB1614
X-OriginatorOrg: team.telstra.com
Received-SPF: none client-ip=203.35.82.208; envelope-from=James.H.Manger@team.telstra.com; helo=ipxcno.tcif.telstra.com.au
X-W3C-Hub-Spam-Status: No, score=-2.1
X-W3C-Hub-Spam-Report: BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, W3C_NW=0.5
X-W3C-Scan-Sig: titan.w3.org 1ceAcL-0003sJ-L6 090fcdce7cd44a80be20dd28a91c7320
X-Original-To: ietf-http-wg@w3.org
Subject: RE: aes128gcm: is the 1st example wrong?
Archived-At: <http://www.w3.org/mid/SYXPR01MB16157B1A0656DE1BDF8F7727E55A0@SYXPR01MB1615.ausprd01.prod.outlook.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/33548
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <http://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>
8bit data is perfectly fine. All zeros *from the end back to the padding delimiter byte* are padding. Bytes before the padding delimiter byte can be anything (including zero). -----Original Message----- From: Daurnimator [mailto:quae@daurnimator.com] Sent: Thursday, 16 February 2017 12:07 PM To: Martin Thomson <martin.thomson@gmail.com> Cc: Julian Reschke <julian.reschke@gmx.de>; Manger, James <James.H.Manger@team.telstra.com>; ietf-http-wg@w3.org Subject: Re: aes128gcm: is the 1st example wrong? On 13 February 2017 at 19:53, Martin Thomson <martin.thomson@gmail.com> wrote: > On 13 February 2017 at 19:09, Julian Reschke <julian.reschke@gmx.de> wrote: >> So... where do I get the padding length from under the new format? > > > You count from the end of the plaintext. All the zeros are padding. > The first non-zero octet (starting from the end) is the end of the > padding and should be 0x01 (regular) or 0x02 (last record). Disallowing 8bit data seems undesireable.
- aes128gcm: is the 1st example wrong? Manger, James
- Re: aes128gcm: is the 1st example wrong? Martin Thomson
- Re: aes128gcm: is the 1st example wrong? Julian Reschke
- Re: aes128gcm: is the 1st example wrong? Martin Thomson
- RE: aes128gcm: is the 1st example wrong? Manger, James
- Re: aes128gcm: is the 1st example wrong? Julian Reschke
- Re: aes128gcm: is the 1st example wrong? Martin Thomson
- Re: aes128gcm: is the 1st example wrong? Daurnimator
- RE: aes128gcm: is the 1st example wrong? Manger, James
- Re: aes128gcm: is the 1st example wrong? Daurnimator