Defending Yourself Against The Wily Wireless Hacker

The Presentation

Defending Yourself Against The Wily Wireless Hacker PDF Presentation for NYCWireless October 27, 2004

Minimum Requirements

Unix/Linux/Mac/Cygwin

No extra software, ssh is standard

Windows

PuTTY - Windows SSH client
OpenSSH for Windows - Windows SSH server and client



Full Bibliography

UNIX/Linux no cost software

TCP wrappers
PPTP Server for Linux
PPTP Client for Linux
IPfilter
IPtables
Simple perl proxy (don't forget to change line 9 to use Socket;)
Alternate perl proxy source (see the above for an edit)
Squid proxy
Free S/WAN
Openswan
OpenVPNcross platform VPN (not in presentation)

Windows no cost software

Kerio Personal Firewall
ZoneAlarm
Sygate Personal Firewall - Acquired by Symantec in August 2005, no longer available at no cost
PuTTY - Windows SSH client
OpenSSH for Windows - Windows SSH server and client
Cygwin - UNIX stuff for Windows
Simple perl proxy (don't forget to change line 9 to use Socket;)
Alternate perl proxy source (see the above for an edit)
Perl for Windows
FreeProxy for Windows
AntiVir
AVG Anti-Virus
Spybot Search & Destroy
Ad-Aware
Spoofstick
Firefox
Maxthon (was MyIE2)
Thunderbird
OpenVPNcross platform VPN (not in presentation)
Windows services for UNIX Like Cygwin, but from Microsoft; a misnomer, it should be called UNIX services for Windows (not in presentation)

Internet Services

Megaproxy - SSL Proxy everything
Panix - ISP that offers shell accounts
DynDNS
ZoneEdit
Display your internet IP address
HotSpot VPN - commercial VPN vendor (not in presentation)

Information

PPTP flaws
PPTP flaws update
OpenSSH source

start -> run -> cmd   C:\> hostname
        your local computer name

start -> run -> cmd   C:\> ipconfig /all
        your local IP address (may not be your internet IP adress)

control panel -> network and internet connections -> network connections ; select interface with right click ; select properties ; select "advanced" tab
         finds Windows XP (pre SP2) firewall (must be done on all interfaces)

control panel -> network and internet connections -> windows firewall
         finds Windows XP SP2 firewall


Remote Desktop Information

This was not part of the prsentation, but came up as questions afterwards. It's included as it's another way to avoid browsing on the untrusted network -- ssh into a trusted machine and then use a full wnidows desktop of that machine.

Once SSH'd into a Windows XP (NOT home edition) box this will enable it to accept Remote Desktop Sessions -

reg add "HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server" /v fDenyTSConnections /t REG_DWORD /d 0x0 /f

This will allow users (on the PC) with admin priveldegs to use remote desktop to access the system. If the user is not an admin you have to add it before hand via Control Panel->System->Remote and then "Select Remote Users..." button.

To use port forwarding with SSH, it's TCP port 3389, so from the commnad like it would be
ssh -L3389:127.0.0.1:3389 windowsxp.box.com Then point the remote desktop client at 127.0.0.1. This only works if the computer you are connecting from does not itself have the remote desktop server running. If it does, you have to turn it off (change 0x0 to 0x1 in the command line above) or it use another port to listen on locally (the first 3389 number to the -L option). Sometimes using another port does not work. Here's an number of options to try:
1) trying to using 127.0.0.2 for the localhost IP instead of 127.0.0.1 in the Remote Desktop Client.
2) Look at the "Compatibility" of the Remote Desktop Client. Find the mstsc.exe progam in \windows\system32 and right click it and select properties. Go to the Compatibility tab and check the "run program in compatability mode for" and then select "Windows 98/Windoes Me" drop down. Click OK. If you cannot change the properties because of access permissions, then copy that program (MSTSC.EXE) and MSTSCAX.DLL to another local directory, like subdirectory under c:\windows\temp (it won't work if it's a network drive) and do the same with the properties and then use THIS modified copy of mstsc program.
3) Use yet another (trusted) machine and forward through that. Do not forget to check "Local ports accept connections from other hosts" box if you use putty or use the -g option if you do command line ssh on that pass through machine. Use this other machines address in the Remote Desktop Client. However you are not in an SSH tunnel from your cueent desktop to the other machine, the tunnil is only from the other machine to the remote desktop machine. So you are dependant on the security of the remote desktop protocol for a portion of the connection.
The remote desktop client software is here if you need it (for Win95, Win98, NT4.0, Windows200). It's here for Mac OS X. And it's here for Linux/UNIX.

My other NYCwireless presentations