Encrypting Router Config Files Over Unsecured Networks
You need to transfer configuration files to a router across an unsecured network. Which protocol should you use to encrypt the files in transit?
Community Insight
The question tests knowledge of secure remote management and file transfer protocols, with the common trap being the selection of HTTP or TFTP due to familiarity rather than security requirements.
To securely transfer configuration files across an unsecured network, SSH is the correct protocol choice as it provides encryption for data in transit. This page explains why SSH is superior to legacy protocols like Telnet and TFTP.
Candidates often mistakenly choose TFTP because it is commonly used for router configurations, failing to recognize that it transmits data in plaintext without any encryption.
Community Discussion (1 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
SSH (Secure Shell) is the only protocol listed that provides end-to-end encryption for both command-line access and file transfers (via SFTP or SCP). When transferring sensitive configuration files over an unsecured network, encrypting the data in transit is critical to prevent eavesdropping and tampering. SSH ensures confidentiality and integrity of the transferred files.Why the Other Options Are Wrong
TFTP (Trivial File Transfer Protocol) operates over UDP and sends all data, including filenames and contents, in clear text, making it insecure for untrusted networks. HTTP also transmits data in plaintext by default; while HTTPS exists, the option specifically lists HTTP, which lacks encryption. Telnet is a legacy remote access protocol that sends all information, including passwords and commands, in clear text, posing a significant security risk.Community Comment Notes
Community consensus strongly supports SSH as the correct answer. As Roattana noted, "SSH (Secure Shell) provides a secure, encrypted channel... safely copy files," highlighting its dual capability for management and secure file transfer. Comments emphasize that TFTP and Telnet lack authentication and encryption features entirely.Exam Strategy
When a question asks for encryption or security over an unsecured network, always look for 'S' or 'Secure' prefixes (like SSH, SFTP, HTTPS, FTPS). Legacy protocols ending in 'tel', 'tftp', or plain 'http' are typically insecure unless specified otherwise.
Frequently Asked Questions
Why isn't TFTP used for secure transfers?
TFTP transmits data in plaintext without encryption or strong authentication, making it vulnerable to interception on unsecured networks.
Can SSH be used for file transfers?
Yes, SSH supports secure file transfer protocols like SFTP and SCP, which encrypt the data during transmission.