SSH uses asymmetric addition AES and DES to achieve data transmission security, and uses HMAC to ensure complete integrity verification of data.

Question

Options

• ATRUE
• BFALSE

• A
  23% (7)
• B
  77% (23)

Explanation

Option B is correct because the statement contains a critical inaccuracy: SSH does not use DES for data transmission security. DES is a legacy symmetric cipher that is considered cryptographically broken and has been deprecated from modern SSH implementations due to its short 56-bit key length. SSH actually uses asymmetric cryptography (such as RSA, ECDSA, or Ed25519) only for the initial key exchange and authentication phase, then switches to symmetric algorithms like AES (not "asymmetric addition AES" as stated) for encrypting bulk data - the phrasing in the question incorrectly labels AES as asymmetric. The HMAC portion of the statement is actually correct - SSH does use HMAC (e.g., HMAC-SHA2) to verify data integrity.

Memory tip: Think of SSH as a two-phase protocol - "Asymmetric to meet, Symmetric to speak" (key exchange uses asymmetric crypto, data transfer uses symmetric like AES). DES is the "dead" cipher - never appear together with modern SSH on an exam without being flagged as wrong.

No community discussion yet for this question.