From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Dave Taht <dave.taht@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Full blown DNSSEC by default?
Date: Sun, 13 Apr 2014 19:57:01 +0200 [thread overview]
Message-ID: <87siph6rki.fsf@toke.dk> (raw)
In-Reply-To: <CAA93jw78phsWs58mHN07SP3213bqQKRv9mJnCbe=ANO9mk1+LQ@mail.gmail.com> (Dave Taht's message of "Sun, 13 Apr 2014 09:40:55 -0700")
[-- Attachment #1: Type: text/plain, Size: 790 bytes --]
Dave Taht <dave.taht@gmail.com> writes:
> Boingo has sent out a mail to all customers saying they were not
> affected, but I do worry a lot about the overall security of
> enterprise wifi and 802.1x ethernet networks in general.
FWIW the 802.1x authentication usually works in one of two modes:
MSCHAPv2 which is Microsoft's challenge/response protocol that never
ships passwords over the wire (setups that authenticate against an
Active Directory, or people who want to support windows clients natively
will run in this mode), or EAP-TTLS which has a second end-to-end TLS
tunnel from the wireless client all the way back to the authentication
server. Presumably the latter will also be vulnerable to heartbleed
until updated, but at least there's another layer of turtles there.
-Toke
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 489 bytes --]
prev parent reply other threads:[~2014-04-13 17:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-13 4:26 Dave Taht
2014-04-13 7:51 ` Török Edwin
2014-04-13 15:04 ` Dave Taht
2014-04-13 10:05 ` Toke Høiland-Jørgensen
2014-04-13 14:57 ` Dave Taht
2014-04-13 17:59 ` Chuck Anderson
2014-04-13 23:24 ` Dave Taht
2014-04-14 9:29 ` Aaron Wood
2014-04-17 21:01 ` Simon Kelley
2014-04-17 21:19 ` Dave Taht
2014-04-20 14:01 ` Chuck Anderson
2014-04-20 15:16 ` Valdis.Kletnieks
2014-04-20 15:41 ` Chuck Anderson
2014-04-13 16:16 ` dpreed
2014-04-13 16:40 ` Dave Taht
2014-04-13 17:57 ` Toke Høiland-Jørgensen [this message]
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=87siph6rki.fsf@toke.dk \
--to=toke@toke.dk \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@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