Google sent me to this well written page: http://www.isaac.cs.berkeley.edu/isaac/wep-faq.html
Why bother with WEP when you have ssh? What are you trying to prevent? I have not gotten anywhere with wireless at home yet, but I've gone to Openssh for all of my wired networking. I've gotten my third cheap wireless card, a Linksys 802.11B this time, and I'm looking forward to seeing if it works and if I can use it as a ssh access point. It would be very cool to be able to shell in wirelessly and X forward through ssh. I've been very happy with KDE graphical support for ssh and sftp. It's not just in their browsers, it's in all of their dialogs. It drags and drops files across file browser splits screens as well as opening foreign documents for local manipulation that saves back without me having to think about it. That local manipulation makes silly things, like a 200GB hard drive on a 90MHz P1, into practical and easy storage devices. It's also nice to be able to use sftp in file opening and email attaching dialog boxes. This way both my wife and I can use our own machines but the same computer for email and yet another single computer for storage transparently. It's so easy. Does anyone remember if and why X forwarding through ssh is insecure? These people think there's nothing wrong with it: http://www.tldp.org/HOWTO/XDMCP-HOWTO/ssh.html but they also use putty, a program that runs on a system that's famous for keylogging malware. It would be nice to know if I can open up X forwarding across my firewall without too much risk. I'm not too paranoid about crackers in my bushes or even next door. I figure my cable box is much more exposed and, like all my insignificant purchases, far more monitored. Still, I do worry that a neighbor might get up to some second rate trouble making for other people if they logged onto a normal WAP. If I knew all of my neighbors well enough to not worry about that, I would not care if they used "my" bandwith to surf the web and email.
