Secure Your Network
By Joshua Drake
A few years back, I learned that using protocols such
as Telnet and FTP was a bad choice. Although both
protocols are widely used, many consumers don't truly
understand their ramifications. The core problem with
Telnet and FTP is that both programs send all data in
plaintext format. If I were a cracker on your network,
I could listen to (sniff) ports 23 and 21 and be
almost guaranteed to see a user log onto a machine and
send a username and password in plaintext. With that
information, I could easily infiltrate your server.
The scary part about the above scenario is that I
don't need to be on your machine to sniff the
information. I only need to be on the network on which
your machine runs.
F-Secure SSH Server/Client
F-Secure
Contact vendor for pricing. |
| Pros:Excellent graphical scp client. Versions for Windows NT and 2000. |
Cons:Doesn't work well with OpenSSH. Relatively expensive. |
A solution to this problem has existed since 1995, and
it's called Secure Shell (SSH).
