Getting Around the 128-bit WEP Failure?
shokk asks: "To get around the failed encryption of WEP 128bit, we're going ahead with setting our own way of encrypting wireless traffic. Because we already have a firewall that laptop users will use to connect to from the outside, we've set up a second mini-firewall parallel to the main firewall, in this case a Netscreen 5, for the access point to hide behind. These people then use their SafeNet SoftPK VPN software to reach through to the main firewall so that their chatty wireless traffic is off on another net and they can still get decent encryption. It brings up the load on the firewall, but then again laptop users are generally not generating much traffic to read their emails and Word documents. How are other people getting around this problem to secure their wireless networks?"
Get the cygwin tools. It includes a port of the actual OpenSSH code. Everything works splendidly, and you get a unix shell and tools for Windows!
Hi-Technical Excellent Taste and Flavor!
Is there any free software available for Windows-platforms to handle the encryption? I think that a SSH tunnel would be a nice way to securely read email, transfer files, etc, but the problem is that I haven't found any free and working SSH client for Windows that supports tunneling.
SSH Secure Shell for Windows is very good and free for private/educational use, but it leaks memory when closing a tunnel, thus local tunnel can be used only certain amount of times until the client hangs. This is very annoying, one can't check POP mail continually because the client hangs in short time.