A network administrator is configuring remote administration for a newly deployed Linux server that must be managed via command line across an untrusted public network. A technician proposes enabling Telnet to allow remote console access, noting that Telnet traffic on its standard port is already open on the firewall. Why is this proposal insecure, and which technology and default port should be implemented instead according to security best practices?
- Telnet transmits credentials and session data in unencrypted cleartext; Secure Shell (SSH) operating over TCP port 22 should be configured instead.Cevap
- BTelnet only functions for graphical desktop sharing; Remote Desktop Protocol (RDP) operating over TCP port 3389 should be configured instead.
- CTelnet requires domain authentication through Active Directory; Remote Assistance (MSRA) operating over TCP port 80 should be configured instead.
- DTelnet sessions can only be established through the Windows Control Panel Credential Manager applet; Virtual Network Computing (VNC) over TCP port 443 should be configured instead.
Cevap
Telnet transmits credentials and session data in unencrypted cleartext; Secure Shell (SSH) operating over TCP port 22 should be configured instead.
Telnet lacks encryption, transmitting all authentication credentials and session commands in cleartext over TCP port 23. To secure command-line administration across untrusted networks, SSH must be used because it encrypts the entire connection using TCP port 22.
Adım Adım Çözüm
Anahtar Kavram
Remote management protocols and default port security (Telnet TCP 23 vs SSH TCP 22)
Tahmini Süre:1m 15s