Re: [Emu] review of draft-ietf-emu-eaptunnel-req-04

"Dan Harkins" <dharkins@lounge.org> Wed, 03 March 2010 21:39 UTC

Return-Path: <dharkins@lounge.org>
X-Original-To: emu@core3.amsl.com
Delivered-To: emu@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 72FC928C1D5 for <emu@core3.amsl.com>; Wed, 3 Mar 2010 13:39:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.137
X-Spam-Level:
X-Spam-Status: No, score=-6.137 tagged_above=-999 required=5 tests=[AWL=0.128, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_MED=-4]
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 Duy3+ELZMuWw for <emu@core3.amsl.com>; Wed, 3 Mar 2010 13:39:06 -0800 (PST)
Received: from colo.trepanning.net (colo.trepanning.net [69.55.226.174]) by core3.amsl.com (Postfix) with ESMTP id 8A96D3A89CB for <emu@ietf.org>; Wed, 3 Mar 2010 13:39:06 -0800 (PST)
Received: from www.trepanning.net (localhost [127.0.0.1]) by colo.trepanning.net (Postfix) with ESMTP id E7FB8200B2; Wed, 3 Mar 2010 13:39:07 -0800 (PST)
Received: from 69.12.173.8 (SquirrelMail authenticated user dharkins@lounge.org) by www.trepanning.net with HTTP; Wed, 3 Mar 2010 13:39:08 -0800 (PST)
Message-ID: <61dde562d3f969274cb5cb5aabafa68b.squirrel@www.trepanning.net>
In-Reply-To: <3A241A6B234BE948B8B474D261FEBC2F0729562D@de01exm68.ds.mot.com>
References: <70e5fb878f73a83d4ba7702e4dc46132.squirrel@www.trepanning.net> <AC1CFD94F59A264488DC2BEC3E890DE509BD34A6@xmb-sjc-225.amer.cisco.com> <3A241A6B234BE948B8B474D261FEBC2F07239D21@de01exm68.ds.mot.com> <a244565651e7f03494eda680a4ae636b.squirrel@www.trepanning.net> <3A241A6B234BE948B8B474D261FEBC2F0729536E@de01exm68.ds.mot.com> <30a512425eb4f0e1140dca0cc92eea30.squirrel@www.trepanning.net> <3A241A6B234BE948B8B474D261FEBC2F0729555F@de01exm68.ds.mot.com> <f78c0ed514c29c3e3cadd46d28731eb5.squirrel@www.trepanning.net> <3A241A6B234BE948B8B474D261FEBC2F0729562D@de01exm68.ds.mot.com>
Date: Wed, 03 Mar 2010 13:39:08 -0800
From: Dan Harkins <dharkins@lounge.org>
To: Hoeper Katrin-QWKN37 <khoeper@motorola.com>
User-Agent: SquirrelMail/1.4.14 [SVN]
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Cc: emu@ietf.org
Subject: Re: [Emu] review of draft-ietf-emu-eaptunnel-req-04
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/emu>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Mar 2010 21:39:07 -0000

  Hi Katrin,

On Wed, March 3, 2010 12:31 pm, Hoeper Katrin-QWKN37 wrote:
> Dan,
>
> OK, I understand that the tunnel provides all these other feats.
>
> But why can't the server authenticate during the tunnel protocol? I
> still don't understand the use case for mutually anonymous tunnels.

  Because it doesn't have the right credential.

> If the server has a certificate why can't it send it to the peer before
> or during the tunnel establishment?

  If the server has a certificate then sending it to the peer
would not really solve any problem. The peer would still need to
have a reason to trust it and we're back to the problem of putting
a trusted certificate in some certificate store. A global PKI to
solve all of our certificate issues still has not materialized.

> If the peer and server share a secret, than this could be used to
> establish the tunnel.

  If the peer and server share a secret they could use one of the PSK
ciphersuites for TLS but those are susceptible to a dictionary attack
and are therefore inappropriate.

  The tunnel is being established with EAP-TLS so we are limited to
TLS ciphersuites and the authentication they provide. If a TLS ciphersuite
was appropriate always and everywhere then we would not need any other
EAP methods, we'd just do EAP-TLS. But that is not the case. Also it is
a requirement to tunnel additional EAP methods inside the tunnel so
obviously there are EAP methods that provide something that a TLS
ciphersuite does not.

> What I am saying is what kind of server authentication credentials could
> be used inside an anonymous tunnel that could not be used to
> authenticate the server in the tunnel protocol? (given that privacy is
> not the issue)

  A low-entropy password that can easily be remembered and entered by a
human with low probability of error.

  Dan.