GzGit in the Zone

Dictionary · Protocols and Ports

Secure and Insecure Protocols

Security · Beginner

A comparison between protocols that encrypt and authenticate traffic and older protocols that send the same kind of data in the clear.

A secure version usually adds encryption, integrity, and a way to check who you reached. The insecure predecessor may do the same job while letting anyone on the path read or change it.

Example: Remote administration should use an encrypted shell rather than a cleartext terminal. Web logins should use protected web traffic rather than a cleartext page.

Common misconception

  • A newer port number does not make a protocol secure. The protection comes from encryption and authentication.

Related terminology

Quiz this category