, 2006-02-09
The average user has no idea of the risks associated with public WiFi hotspots. Here are some very simple tips for them to keep their network access secure.
Expand all |
Post comment
Coffee shop WiFi for dummies
2006-02-13
j (1 replies)
j (1 replies)
RE: Coffee shop - Just say NO to Google!
2006-02-15
Anonymous (1 replies)
Anonymous (1 replies)
Recommending gaim? HAH
2006-02-17
infamous41md (1 replies)
infamous41md (1 replies)
Re: Recommending gaim? HAH
2006-02-19
Roger (1 replies)
Roger (1 replies)
Re: Re: Recommending gaim? HAH
2006-02-20
infamous41md (1 replies)
infamous41md (1 replies)
Re: Re: Re: Recommending gaim? HAH
2006-02-23
Roger (1 replies)
Roger (1 replies)
Re: Re: Re: Re: Recommending gaim? HAH
2006-02-24
infamous41md (1 replies)
infamous41md (1 replies)

The article would have achieved more good if it pushed "always encrypt". This, though, gets into an entirely new topic. For example, email privacy is only partially improved by using secure SMTP and IMAP. That protects two points of possible attack, but every move between SMTP servers and every residence, however brief, on a mail queue somewhere, is another point of possible attack. Better to use end-to-end encryption (ie. PGP).
With respect to SMTP, most ISPs - especially those that are sufficiently savvy as to support encrypted SMTP - will have one or more additional points beyond the standard 25. This is specifically for those mobile clients that are "stuck" behind a firewall that (responsibly, alas!) blocks outbound port 25 access.
There are standard ports assigned to SMTP submission and secure SMTP, but there's often going to be at least one more nonstandard port in use by an ISP as backup (against an especially strict firewall).
The coffee shop staff will know nothing about this, but the user's ISP (or email service provider) should be able to provide the necessary information.
[ reply ]
Link to this comment: http://www.securityfocus.com/comments/columns/385/33121#33121