Tools
Serv-U SSH fingerprint is not showing correctly even it is configured
This article discusses a situation where Serv-U SSH fingerprint is different from what it is configured at the global level.
First published date
4/20/2020 9:32 PM
Last published date
4/20/2020 9:32 PM
Overview
There are some cases where a user is getting different SSH fingerprints from what is generated in Serv-U Global level. It is showing the Serv-U default SSH fingerprint, but the user can connect fine. The SSH private key is generated explicitly in Serv-U but applied at the global level. If you apply it on the domain level, the user will not be able to connect at all. Serv-U log shows just connected and then closed.
Product section
Serv-U Managed File Transfer & Serv-U FTP Server
Cause
- SSH Private key was generated in Serv-U console using 2048 key length
- Generating 2048 and up key length in Serv-U is a known bug of Serv-U
Resolution
Try one of the following options:
1. When generating SSH Private key in Serv-U use only 1024 key length.
2. Use other 3rd party generators like ex. Puttygen when creating higher key length.
Notes: You need to export it to the OpenSSH key after saving the key and then rename the filename to "filename.key." In Puttygen main menu, click Conversion and then select the Export OpenSSH key.
Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment. You elect to use third-party content at your own risk, and you will be solely responsible for the incorporation of the same if any.
1. When generating SSH Private key in Serv-U use only 1024 key length.
2. Use other 3rd party generators like ex. Puttygen when creating higher key length.
Notes: You need to export it to the OpenSSH key after saving the key and then rename the filename to "filename.key." In Puttygen main menu, click Conversion and then select the Export OpenSSH key.
Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment. You elect to use third-party content at your own risk, and you will be solely responsible for the incorporation of the same if any.