IETF Logo Mail Archive

Re: [hybi] on applicability of AES

John Tamplin <jat@google.com> Wed, 12 January 2011 21:00 UTC

Return-Path: <jat@google.com>
X-Original-To: hybi@core3.amsl.com
Delivered-To: hybi@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3C1193A6A93 for <hybi@core3.amsl.com>; Wed, 12 Jan 2011 13:00:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.601
X-Spam-Level:
X-Spam-Status: No, score=-104.601 tagged_above=-999 required=5 tests=[AWL=-1.625, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8CJ47xyAEJzY for <hybi@core3.amsl.com>; Wed, 12 Jan 2011 13:00:23 -0800 (PST)
Received: from smtp-out.google.com (smtp-out.google.com [74.125.121.67]) by core3.amsl.com (Postfix) with ESMTP id 6AAB53A6A82 for <hybi@ietf.org>; Wed, 12 Jan 2011 13:00:21 -0800 (PST)
Received: from kpbe17.cbf.corp.google.com (kpbe17.cbf.corp.google.com [172.25.105.81]) by smtp-out.google.com with ESMTP id p0CL2ejE015992 for <hybi@ietf.org>; Wed, 12 Jan 2011 13:02:40 -0800
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1294866160; bh=M1s3E6IO4E01VbE7ZDAwugKbAVE=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=GyCyG/g+O2KYjdY3WNEzg2B56BWvRkgRgp6hx8Pf/3D4rgWGKtVkhkUNr4x2CfmYS 6lmQILpo0jPUboCjnYgeA==
Received: from yie19 (yie19.prod.google.com [10.243.66.19]) by kpbe17.cbf.corp.google.com with ESMTP id p0CL2K5h032551 for <hybi@ietf.org>; Wed, 12 Jan 2011 13:02:38 -0800
Received: by yie19 with SMTP id 19so445129yie.41 for <hybi@ietf.org>; Wed, 12 Jan 2011 13:02:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=EfOGaqKv/Jp80ja+L6BstWyr1y2TKr5DW69VnU17gkc=; b=dAdQRk1txAmXuxd7Ch//eZlvNsDiwQ6cD1vs4ok4MFg8znDbJR5ma9tRYfQqiNgIlO KeqJay8FPTjxvVH70sPA==
DomainKey-Signature: a=rsa-sha1; c=nofws; d=google.com; s=beta; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=rglTJyok+Aq4K5UyH7qB3NNSV+GPN2jP/zSJjMgx2h5mBrnfpuYzSF/4XC1OPakoJZ l6dD3HJOS9SAnaoxi+qQ==
Received: by 10.151.85.10 with SMTP id n10mr2567019ybl.206.1294866158213; Wed, 12 Jan 2011 13:02:38 -0800 (PST)
MIME-Version: 1.0
Received: by 10.150.212.8 with HTTP; Wed, 12 Jan 2011 13:02:18 -0800 (PST)
In-Reply-To: <A6C1B68A-BF42-4B9D-8434-BF6F070093DD@apple.com>
References: <1294776396.7650.829.camel@ds9.ducksong.com> <02F101E6-7516-4394-BBF8-246FF5FE831B@apple.com> <1294778281.7650.842.camel@ds9.ducksong.com> <484A91D9-2028-4C08-8ABF-9780DFB3A2E8@apple.com> <20110111205545.GB21915@1wt.eu> <AANLkTinjv781Ebb0FMHeaADuJmV+cXtcMRDA0QF89gER@mail.gmail.com> <4D2CDB7E.5030003@caucho.com> <AANLkTi=ize3xAo5o2FxuSajM8QjAg1F93_Zgy-w6at+o@mail.gmail.com> <4D2CDFC4.1020407@caucho.com> <AANLkTimfJxfKAZpOJznpz0o1cPq--x1cQ-4whAwAaweC@mail.gmail.com> <4D2CF617.5080503@callenish.com> <13EDEAC9-925A-4B2E-8AA4-95F3FAC09EA2@apple.com> <4D2D1908.1040306@callenish.com> <4D2D288D.7090103@callenish.com> <0B26D677-1E3F-4B72-B5F8-D818B601ED15@apple.com> <4D2DEA53.6080901@callenish.com> <343AAA15-A0A1-4326-947F-6853F521350A@apple.com> <AANLkTik-G0BYBj6fqabpRyfot7iAufQ9Df2yh5dOBUJq@mail.gmail.com> <A6C1B68A-BF42-4B9D-8434-BF6F070093DD@apple.com>
From: John Tamplin <jat@google.com>
Date: Wed, 12 Jan 2011 16:02:18 -0500
Message-ID: <AANLkTi=NMZmqyTUqxhhm=+_mpq+O49NJ1UTN62vLx2HR@mail.gmail.com>
To: Maciej Stachowiak <mjs@apple.com>
Content-Type: multipart/alternative; boundary="000e0cd56944645c5d0499ac851b"
X-System-Of-Record: true
Cc: "hybi@ietf.org" <hybi@ietf.org>
Subject: Re: [hybi] on applicability of AES
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hybi>
List-Post: <mailto:hybi@ietf.org>
List-Help: <mailto:hybi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Jan 2011 21:00:24 -0000

On Wed, Jan 12, 2011 at 3:05 PM, Maciej Stachowiak <mjs@apple.com> wrote:

> Your description doesn't have enough detail for me to evaluate it. In what
> way would the server nonce be used during the handshake, and in what way do
> you check it?
>

If we were to have Hello frames as have been suggested, in the client's
Hello frame it includes a value computed from the server's nonce.  The
server verifies that value to verify that the client processed it.

Granted, a lazy server implementor could skip that step.  But, we discarded
the amateur programmer requirement long ago, and you could equally say that
a lazy client could just use the same masking key every time, which would be
more damaging to secure operations.

-- 
John A. Tamplin
Software Engineer (GWT), Google

v2.23.0 | Report a Bug | By Email