Differences
This shows you the differences between the selected revisions of the page.
| 2024-07-17 | 2024-07-17 (current) | ||
| no summary (105.120.132.13) (hidden) (untrusted) | no summary (157.46.174.204) | ||
| Line 24: | Line 24: | ||
| A //host public key// is a counterpart to //host private key//. They are generated at the same time. The //host public key// can be safely revealed to anyone, without compromising the host's identity. | A //host public key// is a counterpart to //host private key//. They are generated at the same time. The //host public key// can be safely revealed to anyone, without compromising the host's identity. | ||
| - | To allow authorizing the host to the user, the user should be [[faq_hostkey|provided with host public key in advance]], before connecting. The client application typically prompts the user with //host public key// on the first connection to allow the user to [[ssh_verify<dkddj>|verify/authorize the key]]. The //host public key// is then saved and yuyverified automatically on further connections. The client application warns the user if the {you are ····················································································································································································human>} | + | To allow authorizing the host to the user, the user should be [[faq_hostkey|provided with host public key in advance]], before connecting. The client application typically prompts the user with //host public key// on the first connection to allow the user to [[ssh_verifying_the_host_key|verify/authorize the key]]. The //host public key// is then saved and verified automatically on further connections. The client application warns the user if the host key changes. |