Differences
This shows you the differences between the selected revisions of the page.
| 2018-01-09 | 2018-02-19 | ||
| syntax (martin) | 5.13 was released (martin) | ||
| Line 16: | Line 16: | ||
| * Host key fingerprint: On the first connect you will be prompted to [[ssh_verifying_the_host_key|verify server host key]]. | * Host key fingerprint: On the first connect you will be prompted to [[ssh_verifying_the_host_key|verify server host key]]. | ||
| * You can locate key fingerprint in server's initial start log, when host keys are generated.((Using ''cloud-init'' script.)) Go to the //Boot diagnostics// page and switch to //Serial log// tab. Alternatively use ''[[https://docs.microsoft.com/en-us/powershell/module/azurerm.compute/get-azurermvmbootdiagnosticsdata|Get-AzureRmVMBootDiagnosticsData]]'' command. | * You can locate key fingerprint in server's initial start log, when host keys are generated.((Using ''cloud-init'' script.)) Go to the //Boot diagnostics// page and switch to //Serial log// tab. Alternatively use ''[[https://docs.microsoft.com/en-us/powershell/module/azurerm.compute/get-azurermvmbootdiagnosticsdata|Get-AzureRmVMBootDiagnosticsData]]'' command. | ||
| - | * //With the latest beta version of WinSCP (easier)//: &beta Search for ''-----BEGIN %%SSH%% HOST KEY FINGERPRINTS-----'': \\ <code>-----BEGIN SSH HOST KEY FINGERPRINTS----- | + | * //With the recent versions of WinSCP (easier)//: &recent Search for ''-----BEGIN %%SSH%% HOST KEY FINGERPRINTS-----'': \\ <code>-----BEGIN SSH HOST KEY FINGERPRINTS----- |
| 1024 SHA256:dM0cbKRU1sxYVRTFW8P9/leLzuPndr7Z/fRpiIXBBT8 root@winscpubuntu (DSA) | 1024 SHA256:dM0cbKRU1sxYVRTFW8P9/leLzuPndr7Z/fRpiIXBBT8 root@winscpubuntu (DSA) | ||
| 256 SHA256:eq62XW/s39mrDw8XMNfNsSRUjbK4VhqCRBQeE4tF2WA root@winscpubuntu (ECDSA) | 256 SHA256:eq62XW/s39mrDw8XMNfNsSRUjbK4VhqCRBQeE4tF2WA root@winscpubuntu (ECDSA) | ||
| Line 22: | Line 22: | ||
| 2048 SHA256:xd2ZT5TE/koVle4Gg8UoB2F4tA+SIL/06H98NXV2/+I root@winscpubuntu (RSA) | 2048 SHA256:xd2ZT5TE/koVle4Gg8UoB2F4tA+SIL/06H98NXV2/+I root@winscpubuntu (RSA) | ||
| -----END SSH HOST KEY FINGERPRINTS-----</code> Keep fingerprint for ''ED25519'' key. | -----END SSH HOST KEY FINGERPRINTS-----</code> Keep fingerprint for ''ED25519'' key. | ||
| - | * //With the latest stable version of WinSCP//: Search for ''-----BEGIN %%SSH%% HOST KEY KEYS-----'': \\ <code>-----BEGIN SSH HOST KEY KEYS----- | + | * //With older versions of WinSCP//: Search for ''-----BEGIN %%SSH%% HOST KEY KEYS-----'': \\ <code>-----BEGIN SSH HOST KEY KEYS----- |
| ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBOXBTK0rhHsOnu93hq/YsVBseEvu56WPkCwleBJb4QthaJ7j6Ih4O3dNJHkJ6xv8BxjeTNDoEnwOqJwHXbbmGWw= root@ubuntu | ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBOXBTK0rhHsOnu93hq/YsVBseEvu56WPkCwleBJb4QthaJ7j6Ih4O3dNJHkJ6xv8BxjeTNDoEnwOqJwHXbbmGWw= root@ubuntu | ||
| ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAICv8CYlgCghyr1q+XdGJB560N9FuF4JY4ALHfkR/mktm root@ubuntu | ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAICv8CYlgCghyr1q+XdGJB560N9FuF4JY4ALHfkR/mktm root@ubuntu | ||
| Line 33: | Line 33: | ||
| 256 MD5:e5:27:88:a8:bc:f0:64:bb:3a:e7:71:e6:4d:a1:40:ed <private_ip> (ECDSA) | 256 MD5:e5:27:88:a8:bc:f0:64:bb:3a:e7:71:e6:4d:a1:40:ed <private_ip> (ECDSA) | ||
| 256 MD5:cf:35:d4:78:43:48:26:bf:dc:96:f4:63:8e:ee:35:5b <private_ip> (ED25519) | 256 MD5:cf:35:d4:78:43:48:26:bf:dc:96:f4:63:8e:ee:35:5b <private_ip> (ED25519) | ||
| - | </code> With the latest beta version of WinSCP, you can remove the ''-E md5'' to display SHA-256 fingerprints. &beta | + | </code> //With recent versions of WinSCP,// you can remove the ''-E md5'' to display SHA-256 fingerprints. &recent |
| * If you do not have another trusted instance, you can create new temporary instance, just for the purpose of collecting the keys. First find keys for the new temporary instance, using its initial start log. Then collect keys of the target instance by connecting to it from the temporary instance. After that you can discard the temporary instance. | * If you do not have another trusted instance, you can create new temporary instance, just for the purpose of collecting the keys. First find keys for the new temporary instance, using its initial start log. Then collect keys of the target instance by connecting to it from the temporary instance. After that you can discard the temporary instance. | ||
| * When creating new virtual machine, consider setting up public key authentication by pasting your public key to //%%SSH%% public key// box of the //Configure basic settings// steps. If you want to setup public key authentication later, you have to [[guide_public_key|set it up manually]]. | * When creating new virtual machine, consider setting up public key authentication by pasting your public key to //%%SSH%% public key// box of the //Configure basic settings// steps. If you want to setup public key authentication later, you have to [[guide_public_key|set it up manually]]. | ||