From: Dane Medic <dm70dm@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Secure ad-hoc interface
Date: Fri, 6 Jun 2014 18:04:22 +0200 [thread overview]
Message-ID: <CABsdH_HBzN+NFGfkTDDt7V_8OKRN=EuBG6amJ1M96k5_OVyW7g@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw7c4QZqWkbPuG78tKhvKh0jPuyHZAP18j9nnHd3YJ9stg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1077 bytes --]
I'm not sure which of this patches ->
https://github.com/opentechinstitute/commotion-router/tree/master/patches
but commotion wireless guys have a working adhoc with wpa2
2014-06-06 17:53 GMT+02:00 Dave Taht <dave.taht@gmail.com>:
> On Wed, Jun 4, 2014 at 10:53 PM, Dane Medic <dm70dm@gmail.com> wrote:
> > Hi,
> >
> > are there any plans to add WPA encryption on ibss interface in cerowrt?
>
> Not clear what you mean. adhoc doesn't work with wpa, so far as I know.
>
> I HAVE long thought that shipping with wpa enabled on the main interfaces
> was probably a good idea, but what I'd like in that case is to mandate that
> the wpa keys, ssid, and root password be changed on first install,
> actually.
>
> >
> >
> > Cheers
> >
> > _______________________________________________
> > Cerowrt-devel mailing list
> > Cerowrt-devel@lists.bufferbloat.net
> > https://lists.bufferbloat.net/listinfo/cerowrt-devel
> >
>
>
>
> --
> Dave Täht
>
> NSFW:
> https://w2.eff.org/Censorship/Internet_censorship_bills/russell_0296_indecent.article
>
[-- Attachment #2: Type: text/html, Size: 1965 bytes --]
next prev parent reply other threads:[~2014-06-06 16:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-05 5:53 Dane Medic
2014-06-06 15:53 ` Dave Taht
2014-06-06 16:04 ` Dane Medic [this message]
2014-06-06 16:09 ` Dave Taht
2014-06-06 16:12 ` Valdis.Kletnieks
2014-06-06 16:30 ` Dave Taht
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='CABsdH_HBzN+NFGfkTDDt7V_8OKRN=EuBG6amJ1M96k5_OVyW7g@mail.gmail.com' \
--to=dm70dm@gmail.com \
--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