IETF Logo Mail Archive

Re: [TLS] AES-OCB in TLS [New Version Notification for draft-zauner-tls-aes-ocb-03.txt]

Yaron Sheffer <yaronf.ietf@gmail.com> Mon, 01 June 2015 17:07 UTC

Return-Path: <yaronf.ietf@gmail.com>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1FA1D1B2CBB for <tls@ietfa.amsl.com>; Mon, 1 Jun 2015 10:07:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, 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 lO7v5KcSRgPZ for <tls@ietfa.amsl.com>; Mon, 1 Jun 2015 10:07:42 -0700 (PDT)
Received: from mail-wi0-x236.google.com (mail-wi0-x236.google.com [IPv6:2a00:1450:400c:c05::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9E23C1B2CCE for <tls@ietf.org>; Mon, 1 Jun 2015 10:07:40 -0700 (PDT)
Received: by wizo1 with SMTP id o1so113523195wiz.1 for <tls@ietf.org>; Mon, 01 Jun 2015 10:07:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=8ZSeerlgnu3NYSJ0eY5uMZWDN4+LzeeR/Ax0FQCKoro=; b=MHy01xqW7Tkxb7yNYAu6JGK9xMDAS1rGHefseRHJP8OHpPNMDx5EY/lW1ajICdrh8/ hJU/3RjtJlJAH5AcRoF3cNnOm+I0tYCWhJVP0nzYIYeVhy+ta0GgAX2LC/pI+NB3xsKq qGBHp/CrRmWnGWmvWdF3Yd/UP3a304jZzC2KCEFz61AAgygEmGgn1hT0ay5FTnlSezrp GKMLqVRH3SDCksDs6scoG7nONd8fQGeu9EA1lEpbvPVLlMzsESc5aPz9MD1lauWVpKTl zz4BsqR3JK/aUJA1Y5rDoTHinalzu52PsDc9atDkvEebGMNXlDFeSe+l1R9f4PmchPSz d7lA==
X-Received: by 10.180.72.198 with SMTP id f6mr22253489wiv.21.1433178459440; Mon, 01 Jun 2015 10:07:39 -0700 (PDT)
Received: from [10.0.0.5] (bzq-79-181-148-147.red.bezeqint.net. [79.181.148.147]) by mx.google.com with ESMTPSA id b7sm9567879wjx.47.2015.06.01.10.07.37 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 01 Jun 2015 10:07:37 -0700 (PDT)
Message-ID: <556C9157.4030409@gmail.com>
Date: Mon, 01 Jun 2015 20:07:35 +0300
From: Yaron Sheffer <yaronf.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: noloader@gmail.com, Aaron Zauner <azet@azet.org>
References: <556C4ACD.9040002@azet.org> <CABcZeBNsYmto4F-J0mFoxcq-qfL=NJrvDu67fyY9bpBmRp16mQ@mail.gmail.com> <556C51FC.807@azet.org> <5878037.eTrqDl0Ll5@pintsize.usersys.redhat.com> <556C5881.4080902@azet.org> <CAH8yC8nCCNF9B72yNgM-hOkCYJrc2ZU0PmpeBrnbknKO92OZtA@mail.gmail.com> <556C8320.2010705@azet.org> <CAH8yC8k9Ytf+-=VM0AF36nr3PF_fjTvEpgNRNqAF7xu4zymzRg@mail.gmail.com>
In-Reply-To: <CAH8yC8k9Ytf+-=VM0AF36nr3PF_fjTvEpgNRNqAF7xu4zymzRg@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/tls/u2TRybkfcQq6L_zO9saRVJg39rA>
Cc: "tls@ietf.org" <tls@ietf.org>
Subject: Re: [TLS] AES-OCB in TLS [New Version Notification for draft-zauner-tls-aes-ocb-03.txt]
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tls>, <mailto:tls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tls/>
List-Post: <mailto:tls@ietf.org>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Jun 2015 17:07:44 -0000

On 06/01/2015 07:30 PM, Jeffrey Walton wrote:
>
> If PSK is going to be yanked, then there should probably be an
> non-public-key PAKE alternative.
>
> Jeff
>

Hi Jeff,

PAKE means password-authenticated key exchange, and TLS-PSK is not 
suitable for use with (short, memorable) passwords. See 
https://tools.ietf.org/html/rfc4279#section-7.2

TLS-SRP is the right tool for that. It is public key based but does not 
require the whole PKI code bloat, so may be a good fit for 
resource-constrained devices.

Thanks,
	Yaron

v2.23.0 | Report a Bug | By Email