Or any other method where the pass[hrase doesn't consist of elements that can be cracked by dictionary attacks.

Common mistake people make is setting up a "password" vs. "passphrase" and in either case further making the mistake of only using alphanumeric limiting entropy to <64 possibilities per character. WEP can secure the common man if limits dictate but using "god", "mydogfluffy" type passphrases leaves end runs arround WEP cracking issues never mind lowering WPA to hackable, LOL!

Sideline attacks where the randomness of a generator can be anticipated can negate "secure" passphrase generators but that's not the run-of-the-mill hacker.


On 5/13/2010 8:15 AM, Brian Weeden wrote:
If you are using WPA2 encryption on your WiFi then you have nothing to worry
about in terms of someone cracking it, especially if you use a 64 character
password generated by this site:

https://www.grc.com/passwords.htm

---------------------------
Brian Weeden
Technical Advisor
Secure World Foundation<http://www.secureworldfoundation.org>
+1 (514) 466-2756 Canada
+1 (202) 683-8534 US


On Thu, May 13, 2010 at 11:08 AM, DSinc<[email protected]>  wrote:

Anthony,
I suppose we have different feelings about "complex."
I feel that WIFI is a level of 'complex' I just do not yet require. Nothing
more.
I understand your position and use of WIFI. Yes, a 63-digit master PW would
make much sense. But, even in my 'primitive' wired LAN, my guests have no
access to my LAN clients (tested). Yes, guests can only see my LAN clients,
but can only USE/Access my router/gateway for internet surfing.
Different strokes, I suppose.
Best,
Duncan



On 05/13/2010 10:36, Anthony Q. Martin wrote:

Why so complex, Duncan?

Lock your wireless network down with a hard password and give the guess
a simple one. I use a 63 digit "hex" string for my network from
wireless. For the guest part, which are not allowed to see my computers,
I have a simple one that I can tell them.

On 5/13/2010 10:29 AM, DSinc wrote:

Brian,
TNX. I recall that you did mention your choices before.
Yes, I am thinking of the "guest w/toys" angle. I do not do DHCP at my
router ATM. But, I may now test this feature with a limited range of
addy's for guests to use. I know; more research.
Duncan


On 05/13/2010 06:22, Brian Weeden wrote:

Mix here. Back in 2003 when I lived in Montana I wired my whole house
with
Cat5e and RG6 drops, of course then I moved a year later and have moved
twice more since then (I was in the military until 2007 and my wife
still
is). So for me to put the time in effort into completely wiring a house
each time we move is not very efficient.

Right now I'm running an Apple Airport Extreme which sits in the same
closet
as the main house server (media and backup). That lets me run a wired
connection to that server and the upstairs HTPC which is right above it.
And other things in the A/V closet (like the Xbox 360) get wired as
well .
But everything else in the house (my desktop and laptop, wife's laptop,
iPhone, random other devices) are all Wifi.

The other big reason to have WiF is for visitors. With a 2-mo old and a
2-yr old we are getting a set of grandparents or siblings stopping by
for a
few days every few months, and they all have laptops or netbooks in
tow and
need net access to do work or just surf/email.

I detect from some people a pretty strong aversion to Wireless, and I
would
ask why that is. WiFi is not some new-fangled thing - it's been
around and
in increasingly heavy us for the better part of a decade. Certainly,
there
are some applications that have large enough bandwidth requirements that
wired is preferable. That's why my HTPCs are wired to the content
server.
But for most other things WiFi (especially N) is more than fast
enough and
the lack of wires is a huge benefit.

---------------------------
Brian Weeden
Technical Advisor
Secure World Foundation<http://www.secureworldfoundation.org>
+1 (514) 466-2756 Canada
+1 (202) 683-8534 US



No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 9.0.819 / Virus Database: 271.1.1/2871 - Release Date:
05/13/10 02:26:00




Reply via email to