Re: Security for the IETF wireless network

Bill Fenner <fenner@fenron.com> Fri, 25 July 2014 14:36 UTC

Return-Path: <fenner@fenron.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 30D151B2950 for <ietf@ietfa.amsl.com>; Fri, 25 Jul 2014 07:36:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.977
X-Spam-Level:
X-Spam-Status: No, score=-101.977 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, USER_IN_WHITELIST=-100] 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 5CxWsyC-N6GI for <ietf@ietfa.amsl.com>; Fri, 25 Jul 2014 07:36:47 -0700 (PDT)
Received: from mail-qg0-f53.google.com (mail-qg0-f53.google.com [209.85.192.53]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BC11C1B2995 for <ietf@ietf.org>; Fri, 25 Jul 2014 07:36:30 -0700 (PDT)
Received: by mail-qg0-f53.google.com with SMTP id q107so5082313qgd.40 for <ietf@ietf.org>; Fri, 25 Jul 2014 07:36:30 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=B6gkT9aT4nAG0T69QYh7ch+Mcc3o1VE1FajH9BDbQ4o=; b=FeJjAAgKwkRpzhG894QDOaB+LUYE5BJyVoGscNIpRT16GzocA5A9uy+hLZ3TQao9Vz kPrbw0BTajiDMSHwlc5yospkZC7NNCZFXtcNd62hPOFhIZatF4Ph8Lqr5agAq4t0E2Ta qUCpj9GOv2V5OCX1Gas+0uF9t8ppKqpYjIlATul2/ShpVbLqe9tXVLYM6xz2aYWK0WYO 6bdyfanim8FKBSbwnFtK+3DH6LDj7UYVt17US4si4ukouU2yQurhDIKS2QruSyAY68rm OMlys6w/mtYcbX8hx/9Pi9oRvaU3xD/Zo/ePbN2i7cijm9peCoDsb3OWb1berPWXJEgd K9FQ==
X-Gm-Message-State: ALoCoQnypfJ1Gu7QfTxVgvUff4GoQ3J+GGfl9Y505R7VBvOx+hJFQKpR8LRpHLWgpDdzf3vozNeP
MIME-Version: 1.0
X-Received: by 10.224.46.8 with SMTP id h8mr20647417qaf.6.1406298989924; Fri, 25 Jul 2014 07:36:29 -0700 (PDT)
Received: by 10.224.204.72 with HTTP; Fri, 25 Jul 2014 07:36:29 -0700 (PDT)
In-Reply-To: <53D2687A.8030608@gmail.com>
References: <0FE63216-9BE8-450F-80FB-D1DB6166DFEF@ietf.org> <53D17359.2030505@gmail.com> <CFF7BAFE.28A14%wesley.george@twcable.com> <53D25789.8000804@restena.lu> <CAATsVbY44t7QvDNe4UcBfM1MpzkphZYCyHPz=Mwax95fSpjmFg@mail.gmail.com> <53D2687A.8030608@gmail.com>
Date: Fri, 25 Jul 2014 10:36:29 -0400
Message-ID: <CAATsVbbY7p5bsaFgju+jcsi9WP31=Wnh+Eo0cuJRaCNBuuDZ_w@mail.gmail.com>
Subject: Re: Security for the IETF wireless network
From: Bill Fenner <fenner@fenron.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary="001a11c36122be277404ff057fbe"
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/90Iw14KjMkvDE9qgJG7grhBa0Nc
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Jul 2014 14:36:49 -0000

On Fri, Jul 25, 2014 at 10:23 AM, Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> On 26/07/2014 02:12, Bill Fenner wrote:
> > On Fri, Jul 25, 2014 at 9:11 AM, Stefan Winter <stefan.winter@restena.lu
> >
> > wrote:
> >
> >> Hi,
> >>
> >>> To use 802.1X:
> >>>
> >>> Associate to SSID: ietf.1x OR ietf-a.1x
> >>> Use TTLS or PEAP/MSCHAPv2
> >>> Do Not Verify Server Cert and we won't verify yours :)
> >>> ^^^^^^^^^^^^^^^^^^^^^^^^^
> >> I recall some email threads with the NOC about this sentence. It's IMHO
> >> not a message the IETF should promote.
> >>
> >
> > I believe there's a reasonable amount of support for opportunistic
> > encryption in the IETF.
> >
> > The desired incremental delta between the "ietf" open SSID and the
> > "ietf.1x" encrypted SSID is the addition of encryption.  The additional
> > validation of "is this really the IETF" has been a non-goal.
>
> Fair enough. But that doesn't change the fact that my box doesn't
> work that way by default and apparently I have to find out how
> to override it. Being human, I reverted to the unencrypted network
> instead.
>
> Sorry, I assumed that this was just an annoying dialog and there was a
checkbox for "do it anyway".  We will have to find a way to manage the
usability on Windows, whether that means "buy a cert from someone who is in
Microsoft's default trust list too" or "provide instructions for Windows
users" or what.

  Bill