[Novalug] best way to secure wireless?

[Paul M.]

Personally I'm in favor of using a VPN like OpenVPN. SSL and IPSEC
have been looked at and targeted for longer than the current batch of
"built in" wireless security protos. Of course it does make initial
client more difficult in some situations. The counter point to this is
that some OSs and/or hardware doesn't support a given protocol.
However a VPN client like OpenVPN can run on Linux/Windows/OSx.
Another option is to create two wireless networks. One that is
unsecured for guests and a secured one for your own machines. Most
business and geek guests will have their own VPN back home to secure
their connections. Its also a lot less of a hassle to let someone
online.

Regarding the "RIAA/MPAA could come after you"
If you didn't give them permission to use your internet connection for
illegal activities than it would be hard to hold you legal
responsible. If you left your door unlocked you aren't responsible for
someone breaking in, stealing a knife, and then stabbing someone.
There could also be some protection relating to common carrier status
if you keep logs.

-Paul

On 11/26/06, Brandon Saxe <brandon20va at yahoo.com> wrote:
> What's the best (in your opinion) way to secure wireless 802.11x networks in
> a mix hardware environment with the following support requirements:
>
> o Legacy hardware that consists of devices only supporting WEP 64 bit
> o Legacy hardware that consists of devices supporting WEP 64/128
> o Newer hardware that can do WPA
> o Linux/Windows clients
> o IPSec VPN clients that need to connect to outside networks
> o L2TP/PPTP VPN clients to outside networks possible
>
> Is there a way all this stuff can exist together on a secure, wireless
> network?
>
> Obviously, the least common denominator in this scenario is the WEP 64-bit
> devices. Is there a software solution you'd recommend?
>
> Thanks,
>   Brandon
>
> _______________________________________________
> Novalug mailing list
> Novalug at calypso.tux.org
> http://calypso.tux.org/cgi-bin/mailman/listinfo/novalug
>
>
>