Re: [TLS] Issue 56: AES as MTI

To: tls at ietf.org
Subject: Re: [TLS] Issue 56: AES as MTI
From: Mike <mike-list at pobox.com>
Date: Wed, 12 Sep 2007 17:26:28 -0700
Cc:
In-reply-to: <20070912232636.2B5FE33C21@delta.rtfm.com>
List-archive: <http://www1.ietf.org/pipermail/tls>
List-help: <mailto:tls-request@lists.ietf.org?subject=help>
List-id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.lists.ietf.org>
List-post: <mailto:tls@lists.ietf.org>
List-subscribe: <https://www1.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@lists.ietf.org?subject=subscribe>
List-unsubscribe: <https://www1.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@lists.ietf.org?subject=unsubscribe>
References: <20070912231150.ED1D533C21@delta.rtfm.com> <65C7072814858342AD0524674BCA2CDB0D2E6E3E@rsana-ex-hq2.NA.RSA.NET> <20070912232636.2B5FE33C21@delta.rtfm.com>
User-agent: Thunderbird 2.0.0.6 (Windows/20070728)

The current algorithm is 3DES_EDE_CBC. I would imagine we would use
AES_128_CBC. It's a much easier substitution than GCM and most
TLS stacks already support AES-CBC.


I support AES-CBC in my implementation, but don't yet support GCM,
just as one more data point for your decision.

However, is 128-bit AES as strong as 192-bit 3DES?

Mike

_______________________________________________
TLS mailing list
TLS at lists.ietf.org
https://www1.ietf.org/mailman/listinfo/tls

Follow-Ups:
- [TLS] Re: Issue 56: AES as MTI
  - From: Simon Josefsson

References:
- [TLS] Issue 56: AES as MTI
  - From: Eric Rescorla
- Re: [TLS] Issue 56: AES as MTI
  - From: Eric Rescorla

Prev by Date: RE: [TLS] Issue 56: AES as MTI
Next by Date: [TLS] Re: Review of draft-santesson-tls-gssapi-03
Previous by thread: RE: [TLS] Issue 56: AES as MTI
Next by thread: [TLS] Re: Issue 56: AES as MTI
Index(es):
- Date
- Thread

Re: [TLS] Issue 56: AES as MTI

Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.