Hey Hey,

There will always be systems that use plain text that you have to use... The idea is to trust your local network (the odds of the data being sniffed as it crosses the Internet is much less likely) and trust the recipient and do your best (at least with the local network) to ensure it's secure..

As far as what's plain text... that's endless, some of the major ones are: HTTP, FTP, Telnet, POP3, SMTP, IRC... however there are options for most of these..

Instead of using HTTP, use HTTPS... if a site doesn't use it, question why or don't use the site... also ensure that the site isn't using it's own local encryption methods (then HTTPS may not be needed)

Instead of FTP use SFTP... most places these days will provide it as an alternative

Instead of telnet use SSH... there will seldom be times when telnet is actually needed, SSH should always be used instead...

Instead of POP3 use pop3s... if that isn't an option investigate a new mail provider..

Instead of SMTP use smtps... again same as above..

Instead of IRC use IRC over SSL or move to SILC..

However the number of plaintext protocols is practically endless... especially as people devise their own apps.... The idea is to control as much as you can and have a little faith....

For things like personal encryption you could encrypt your email (which you should do anyways as it crossing the wire in plain text can be as bad as your password crossing)..

Anyways you have to realize that plain-text protocols aren't what you should be afraid of... there are many things out there that are much worse...

Secure your local network and you've done everything you can... Everyone uses plain text and, so far, most of us have not had a problem with it..

Peace,
HT