public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Stroller <stroller@stellar.eclipse.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Locking down a wireless network
Date: Fri, 30 Jan 2009 22:37:39 +0000	[thread overview]
Message-ID: <F92E134B-8949-497C-95F5-8E5D5DEBDE8D@stellar.eclipse.co.uk> (raw)
In-Reply-To: <49bf44f10901290940p3ab050cep2e5bd985ee901fde@mail.gmail.com>


On 29 Jan 2009, at 17:40, Grant wrote:

> My Gentoo router's wireless network is encrypted via WPA and doesn't
> DHCP.  I'd like to take this a step further in case my WPA key gets
> hacked.

What makes you think your WPA key is likely to get hacked?

As I'm reading it, if you use a long random password & unique SSID WPA  
is quite secure.

It should be possible to implement WPA2 on a Linux-based AP. I would  
use 64 random hex digits for your PSK & stop worrying about it.

MAC address filtering is worthless. I would install a DHCP server &  
save yourself the hassle of setting IP addresses on any devices that  
are used elsewhere. Anyone who breaks WPA (which I consider extremely  
unlikely assuming the criteria I've described) is not going to be  
troubled by such measures.

Stroller.




      parent reply	other threads:[~2009-01-30 22:37 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-29 17:40 [gentoo-user] Locking down a wireless network Grant
2009-01-29 17:47 ` Dan Cowsill
2009-01-29 17:50 ` Paul Hartman
2009-01-29 20:30   ` Grant
2009-01-29 20:39     ` Saphirus Sage
2009-01-29 20:39   ` Grant
2009-01-29 20:48     ` Saphirus Sage
2009-01-29 20:58     ` Paul Hartman
2009-01-29 21:02       ` Saphirus Sage
2009-01-29 22:15       ` Grant
2009-01-30 16:25       ` Grant
2009-02-03 21:22         ` Paul Hartman
2009-01-29 18:11 ` Mark Knecht
2009-01-29 20:11   ` Paul Hartman
2009-01-30 22:37 ` Stroller [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=F92E134B-8949-497C-95F5-8E5D5DEBDE8D@stellar.eclipse.co.uk \
    --to=stroller@stellar.eclipse.co.uk \
    --cc=gentoo-user@lists.gentoo.org \
    /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