Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu
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, 06 Jun 2014 12:12:50 -0400	[thread overview]
Message-ID: <6835.1402071170@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Fri, 06 Jun 2014 08:53:12 -0700." <CAA93jw7c4QZqWkbPuG78tKhvKh0jPuyHZAP18j9nnHd3YJ9stg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 536 bytes --]

On Fri, 06 Jun 2014 08:53:12 -0700, Dave Taht said:

> Not clear what you mean. adhoc doesn't work with wpa, so far as I know.

I'm not even sure what it would *mean*, given the administrative model
implied by WPA and the admin model implied by adhoc..

> 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.

That's actually a Really Good Idea.

[-- Attachment #2: Type: application/pgp-signature, Size: 848 bytes --]

  parent reply	other threads:[~2014-06-06 16:13 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
2014-06-06 16:09     ` Dave Taht
2014-06-06 16:12   ` Valdis.Kletnieks [this message]
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=6835.1402071170@turing-police.cc.vt.edu \
    --to=valdis.kletnieks@vt.edu \
    --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