From: Ranganathan Krishnan <rk@selwastor.com>
To: Dave Taht <dave.taht@gmail.com>, Mitar <mmitar@gmail.com>,
Christopher Byrd <chris@riosec.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [Ow-tech] Open secure wireless
Date: Wed, 17 Jun 2015 15:31:03 -0700 [thread overview]
Message-ID: <35B0D798-27F2-4146-A78A-AA0008C87DF9@selwastor.com> (raw)
In-Reply-To: <CAA93jw7VWSAJz4HUjW0BwO+=X1QK-4+s=v0bTPL4f+-Wx2WTRw@mail.gmail.com>
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 -- even
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 <dave.taht@gmail.com> 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 <mmitar@gmail.com>
> 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-Wireless.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äht
> 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
next prev parent reply other threads:[~2015-06-17 22:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAKLmikNCL9eOb+V7fU0gvF7g8U4sFWiTEMPbX7aTrfqp7=OAkA@mail.gmail.com>
2015-06-17 15:47 ` [Cerowrt-devel] Fwd: " Dave Taht
2015-06-17 22:31 ` Ranganathan Krishnan [this message]
2015-06-18 21:11 ` [Cerowrt-devel] " Christopher Byrd
2015-06-18 21:35 ` Mitar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=35B0D798-27F2-4146-A78A-AA0008C87DF9@selwastor.com \
--to=rk@selwastor.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=chris@riosec.com \
--cc=dave.taht@gmail.com \
--cc=mmitar@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox