From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ie0-x235.google.com (mail-ie0-x235.google.com [IPv6:2607:f8b0:4001:c03::235]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id E960321F606 for ; Thu, 18 Jun 2015 14:34:47 -0700 (PDT) Received: by iefd2 with SMTP id d2so7047892ief.2 for ; Thu, 18 Jun 2015 14:34:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=R3u6rWBy8t57Bm3c6MavKPf0+RKEtVyO3plCafyw/wI=; b=gaNgue8EJPRHcvepWDP88QqVpY55XjYlqqHnhkbNtGNtg/n2j2nrEoNhP283GREbvQ huQe4mSrXXIOthDhFV1uYhNpAEnBPp77Dwe3fJey6AfATmHhSa1A+4K3297bex5Dzeox GgLDVZdhpIcfMtkpGfEITNxow5Onldids4pG4EYOC8EYNc/CCQbIa0018tPP+hTPQB+C +PxSh0cctw2pt4dFOlu3QwAX/5034Kb76iyjCEC5IKctOqSiChBiqGOkNlWVPPioYnKo GSIEoxvMaWai0FXoxpb/gQd74bUTr7kziQBgfmYtVs62pY3eyxTcd5x3ZeY9LH38Iqyu OUgQ== MIME-Version: 1.0 X-Received: by 10.43.34.205 with SMTP id st13mr8178335icb.4.1434663286451; Thu, 18 Jun 2015 14:34:46 -0700 (PDT) Received: by 10.107.32.19 with HTTP; Thu, 18 Jun 2015 14:34:46 -0700 (PDT) In-Reply-To: References: <35B0D798-27F2-4146-A78A-AA0008C87DF9@selwastor.com> Message-ID: From: Mitar To: Christopher Byrd Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Mailman-Approved-At: Sat, 15 Aug 2015 08:48:05 -0700 Cc: "cerowrt-devel@lists.bufferbloat.net" Subject: Re: [Cerowrt-devel] [Ow-tech] Open secure wireless X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Date: Thu, 18 Jun 2015 21:35:16 -0000 X-Original-Date: Thu, 18 Jun 2015 14:34:46 -0700 X-List-Received-Date: Thu, 18 Jun 2015 21:35:16 -0000 Hi! So, what can we do to change this? Mitar On Thu, Jun 18, 2015 at 2:11 PM, Christopher Byrd wrote: > > Yep, I'm here. Thanks for reading my research! If there are any questions > about the technique, I'd be glad to answer them. While technically Open > Secure Wireless works, the user experience is not acceptable. The biggest > hurdle remains industry standards and client support. > > Christopher > > On Wed, Jun 17, 2015 at 5:31 PM, Ranganathan Krishnan > wrote: >> >> >> >> We have Chris Byrd from Riosec on the ow-tech mailing list. Check >> out this thread from him last year : >> >> https://lists.eff.org/pipermail/ow-tech/2014-May/000031.html >> >> I have this feature enabled on the Openwireless APs. What is needed >> is a campaign with the Client manufactureres (Google, Cyanogen, >> Apple etc) to get them to fix the bugs in their implementation that >> cause their clients to abort if no client certificate is installed -- ev= en >> though the connection would succeed since the server will never >> request the client cert. >> >> If there is interest in sustaining such a campaign with the Client >> manufacturers, I will be happy to contribute. >> >> Cheers, >> Ranga >> >> >> >> >> On Jun 17, 2015, at 8:47 AM, Dave Taht wrote: >> >> > In the alphabet soup of wireless standards, I had not heard of 802.11u >> > before now. >> > >> > http://www.riosec.com/articles/open-secure-wireless-20 >> > >> > >> > ---------- Forwarded message ---------- >> > From: Mitar >> > Date: Wed, Jun 17, 2015 at 4:29 AM >> > Subject: [Ow-tech] Open secure wireless >> > To: ow-tech@lists.eff.org >> > >> > >> > Hi! >> > >> > Reading this old post: >> > >> > https://www.eff.org/deeplinks/2011/04/open-wireless-movement >> > >> > I wanted to point some research done on this some time ago: >> > >> > http://www.riosec.com/articles/Open-Secure-Wireless >> > >> > http://www.riosec.com/articles/Open-Secure-Wireless/Open-Secure-Wirele= ss.pdf >> > >> > And also some progress: >> > >> > http://www.riosec.com/articles/open-secure-wireless-20 >> > >> > If you are not doing that already, I think EFF should get on board of >> > supporting those changes to the standard. >> > >> > (BTW, originally, as presented in 1.0 paper, WiFi standard does allow >> > open and secure connections, just no operating system really >> > implements it because they all first prompt for the password, before >> > trying to connect to the encrypted WiFi network to figure out the >> > password is really required.) >> > >> > >> > Mitar >> > >> > -- >> > http://mitar.tnode.com/ >> > https://twitter.com/mitar_m >> > _______________________________________________ >> > Ow-tech mailing list >> > Ow-tech@lists.eff.org >> > https://lists.eff.org/mailman/listinfo/ow-tech >> > >> > >> > -- >> > Dave T=C3=A4ht >> > What will it take to vastly improve wifi for everyone? >> > https://plus.google.com/u/0/explore/makewififast >> > _______________________________________________ >> > Cerowrt-devel mailing list >> > Cerowrt-devel@lists.bufferbloat.net >> > https://lists.bufferbloat.net/listinfo/cerowrt-devel >> > --=20 http://mitar.tnode.com/ https://twitter.com/mitar_m