Encrypting Router Config Files Over Unsecured Networks
Short answer
C SSH provides the necessary encryption to securely transfer configuration files across an unsecured network.
Question
Which protocol should you use to encrypt the files in transit?
Key Takeaways
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.
Common mistake: 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.
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?
Can SSH be used for file transfers?
Discussion 1 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 1
-
Roattana 👍 1 Answered C• SSH (Secure Shell) provides a secure, encrypted channel over an unsecured network to manage devices and safely copy files (using underlying protocols like SFTP or SCP). • TFTP sends data in plaintext without any encryption or authentication. • HTTP transfers data in plaintext by default (unlike its secure counterpart, HTTPS). • Telnet sends all data, including login credentials and configurations, in unencrypted plaintext.
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.