ACE-P-ALE1-04 practice question 19 of 35

True or false: an SSH private key should never be shared with other users or host systems.

Full set: 100 questions
Answer options
A: TRUE
B: FALSE
Correct Answer:
TRUE
Explanation

The fundamental security principle of public-key cryptography, which SSH utilizes, is based on the strict confidentiality of the private key. The private key is the sole proof of a user's identity. Sharing it with other users or distributing it across multiple systems is equivalent to sharing a master password; it allows anyone with a copy of the key to impersonate the original owner, negating accountability and creating a significant security vulnerability. The private key must remain secret and in the exclusive control of its owner.

Why Incorrect

Stating that this is false would imply that there are acceptable scenarios for sharing a private key. From a security best practices perspective, this is incorrect. Any situation that seems to require sharing a private key (e.g., a shared service account) should be addressed with alternative, more secure methods, such as creating dedicated keys for each user or service, rather than compromising the integrity of a single private key.

References

1. Arista Networks Official Documentation: In the Arista EOS User Manual, the section on Secure Shell (SSH) configuration implicitly supports this principle. The architecture of SSH key-based authentication is designed around a user-specific key pair. The documentation states, "The private key is known only to the user and should be kept secret." This underscores the principle that the key is a private, non-sharable credential.

Source: Arista EOS User Manual, Release 4.27.1F, "Configuring Secure Shell," Page 1531.

2. IETF Standards (RFC): The official standard for the SSH authentication protocol explicitly details a mechanism where the client proves possession of the private key without ever transmitting the key itself. The security of the entire method relies on the key remaining private to the client.

Source: IETF RFC 4252, "The Secure Shell (SSH) Authentication Protocol," Section 7. The client "MUST have possession of the private key" to generate a signature, which proves identity. The protocol's security model collapses if possession is not exclusive.

3. University Courseware: Reputable computer science programs teach this as a foundational concept in network security. For example, MIT's courseware on computer security explains that the entire basis of public-key authentication is that the private key is kept secret by its owner.

Source: MIT OpenCourseWare, 6.858 Computer Systems Security, Fall 2014. Lecture 13: "Network Security I," discusses the SSH protocol where the client proves it knows a secret (the private key) without revealing it. Sharing the secret invalidates the proof.

Scroll to Top