|
RIPE 47 Wireless Security |
|
Reminder: Don't Use Cleartext Passwords!
Packet Transport Over the Internet Isn't Secure
The wireless network at the RIPE meetings needs to be considered as an unsecure
network because it is very easy to sniff the network traffic and get passwords.
In addition, because we're using a temporary network installed in an open
meeting area with physical access available to anyone, no guarantees
can be made about its physical security. This means that end-to-end
encryption (e.g., ssh, IPSEC, https) is crucial to protecting your data and
privacy.
For these reasons, we recommend the following:
- Use ssh for any terminal connection. If you must connect to a system
that doesn't support ssh, at least ssh to an intermediate system to make
sure that the portion crossing the local network is encrypted.
- Use scp or sftp instead of non-anonymous ftp; remember that
ftp passwords are sent in the clear.
- If using IMAP or POP, configure your mailer to use SSL, or at least APOP.
- If using a web-based interface (e.g., Exchange), make sure to use the https:
URL.
- Remember that any form submission or web password entry may cross the network
in the clear.
|