Lpic 1 Linux Administrator · Free Practice Question Medium
Question 4
- A Execute ssh -o "StrictHostKeyChecking=no" 192.168.6.52 to bypass the host identity check.
- B Delete the offending key from the ~/.ssh/known_hosts file before reconnecting.
- C Reset the remote host's private key and reconnect.
- D Connect using a different user account on the remote system.
- E Reconnect with the ssh -f option to force the connection without checking the key.
Reveal correct answer
Correct answer: B
A. By using the "StrictHostKeyChecking=no" option with the ssh command, you are bypassing the host identity check, which can compromise the security of the connection. It is not recommended to disable host key checking as it exposes you to potential security risks.
B. Deleting the outdated key from the ~/.ssh/known_hosts file is the correct approach to resolve the warning and successfully connect to the host. This action ensures that the host key is updated and matches the current fingerprint, allowing for a secure connection.
C. Resetting the remote host's private key is not a practical solution for resolving the warning about the outdated public key fingerprint. This action would require coordination with the remote host administrator and may not be necessary to establish a successful connection.
D. Connecting using a different user account on the remote system does not address the issue of the outdated public key fingerprint. The warning is related to the host identity and key mismatch, not the user account used for the connection.
E. Reconnecting with the ssh -f option to force the connection without checking the key is not a recommended solution. Ignoring the key verification process can expose you to security risks, as it bypasses the essential step of verifying the host's identity before establishing the connection.
Discussion
Think the marked answer is wrong, or have a better explanation? Share it below — comments appear after review.
