By dbb - 5/15/2024 8:47:18 AM
Hi, we updated to the latest version of Fortress SSH Server, version 5 Build 10 Revision 4249. After the update and after regenerating the keys to from 1024 bits to 2048 bits, the connection time has significantly increased. It now takes 30 - 40 seconds for a connection to complete. Any suggestions on what may be causing this? Thanks.
|
By Technical Support Group (TSG) - 5/17/2024 2:29:01 PM
+xHi, we updated to the latest version of Fortress SSH Server, version 5 Build 10 Revision 4249. After the update and after regenerating the keys to from 1024 bits to 2048 bits, the connection time has significantly increased. It now takes 30 - 40 seconds for a connection to complete. Any suggestions on what may be causing this? Thanks.
Hello,
Please try a hidden setting we have. Using regedit.exe, go to HKEY_LOCAL_MACHINE\SOFTWARE\PragmaSystems\SSHD. Add the string value "FIPSType", if it does not exist and give it a value of "1". This will use a different crypto library. Please let me know if this improves the connection time.
|
By dbb - 5/22/2024 7:45:49 AM
+x+xHi, we updated to the latest version of Fortress SSH Server, version 5 Build 10 Revision 4249. After the update and after regenerating the keys to from 1024 bits to 2048 bits, the connection time has significantly increased. It now takes 30 - 40 seconds for a connection to complete. Any suggestions on what may be causing this? Thanks. Hello, Please try a hidden setting we have. Using regedit.exe, go to HKEY_LOCAL_MACHINE\SOFTWARE\PragmaSystems\SSHD. Add the string value "FIPSType", if it does not exist and give it a value of "1". This will use a different crypto library. Please let me know if this improves the connection time.
Hi, thank you for the reply. Unfortunately that did not resolve the issue. Would you have any other recommendations?
|
By Technical Support Group (TSG) - 5/24/2024 10:43:18 AM
+x+x+xHi, we updated to the latest version of Fortress SSH Server, version 5 Build 10 Revision 4249. After the update and after regenerating the keys to from 1024 bits to 2048 bits, the connection time has significantly increased. It now takes 30 - 40 seconds for a connection to complete. Any suggestions on what may be causing this? Thanks. Hello, Please try a hidden setting we have. Using regedit.exe, go to HKEY_LOCAL_MACHINE\SOFTWARE\PragmaSystems\SSHD. Add the string value "FIPSType", if it does not exist and give it a value of "1". This will use a different crypto library. Please let me know if this improves the connection time. Hi, thank you for the reply. Unfortunately that did not resolve the issue. Would you have any other recommendations?
Go to the Logging page on the Local Server Configuration program. Turn on Server Operation Logging and set the level to 6. Configure a directory for the log files. I recommend a directory outside of the Program Files directory. Make sure that the ssh users have write access to the configured directory.
Run a test where you get the long logon, then send me the file at support@pragmasys.com. Please do not send more than 10-20 log files.
|
By dbb - 5/27/2024 1:05:56 PM
+x+x+x+xHi, we updated to the latest version of Fortress SSH Server, version 5 Build 10 Revision 4249. After the update and after regenerating the keys to from 1024 bits to 2048 bits, the connection time has significantly increased. It now takes 30 - 40 seconds for a connection to complete. Any suggestions on what may be causing this? Thanks. Hello, Please try a hidden setting we have. Using regedit.exe, go to HKEY_LOCAL_MACHINE\SOFTWARE\PragmaSystems\SSHD. Add the string value "FIPSType", if it does not exist and give it a value of "1". This will use a different crypto library. Please let me know if this improves the connection time. Hi, thank you for the reply. Unfortunately that did not resolve the issue. Would you have any other recommendations? Go to the Logging page on the Local Server Configuration program. Turn on Server Operation Logging and set the level to 6. Configure a directory for the log files. I recommend a directory outside of the Program Files directory. Make sure that the ssh users have write access to the configured directory. Run a test where you get the long logon, then send me the file at support@pragmasys.com. Please do not send more than 10-20 log files.
The files have been sent.
|
By Technical Support Group (TSG) - 5/28/2024 8:52:15 AM
+x+x+x+x+xHi, we updated to the latest version of Fortress SSH Server, version 5 Build 10 Revision 4249. After the update and after regenerating the keys to from 1024 bits to 2048 bits, the connection time has significantly increased. It now takes 30 - 40 seconds for a connection to complete. Any suggestions on what may be causing this? Thanks. Hello, Please try a hidden setting we have. Using regedit.exe, go to HKEY_LOCAL_MACHINE\SOFTWARE\PragmaSystems\SSHD. Add the string value "FIPSType", if it does not exist and give it a value of "1". This will use a different crypto library. Please let me know if this improves the connection time. Hi, thank you for the reply. Unfortunately that did not resolve the issue. Would you have any other recommendations? Go to the Logging page on the Local Server Configuration program. Turn on Server Operation Logging and set the level to 6. Configure a directory for the log files. I recommend a directory outside of the Program Files directory. Make sure that the ssh users have write access to the configured directory. Run a test where you get the long logon, then send me the file at support@pragmasys.com. Please do not send more than 10-20 log files. The files have been sent.
Thanks for the files. The delay is occuring at the loading of the crypto library. Please try my first suggestion, but use a value of 2, instead of 1. If that still has a delay, try turning off FIPS mode on the General Settings page of the Local Server Configuration program and let me know if that fixes the issue.
|
By dbb - 5/28/2024 11:48:08 AM
+x+x+x+x+x+xHi, we updated to the latest version of Fortress SSH Server, version 5 Build 10 Revision 4249. After the update and after regenerating the keys to from 1024 bits to 2048 bits, the connection time has significantly increased. It now takes 30 - 40 seconds for a connection to complete. Any suggestions on what may be causing this? Thanks. Hello, Please try a hidden setting we have. Using regedit.exe, go to HKEY_LOCAL_MACHINE\SOFTWARE\PragmaSystems\SSHD. Add the string value "FIPSType", if it does not exist and give it a value of "1". This will use a different crypto library. Please let me know if this improves the connection time. Hi, thank you for the reply. Unfortunately that did not resolve the issue. Would you have any other recommendations? Go to the Logging page on the Local Server Configuration program. Turn on Server Operation Logging and set the level to 6. Configure a directory for the log files. I recommend a directory outside of the Program Files directory. Make sure that the ssh users have write access to the configured directory. Run a test where you get the long logon, then send me the file at support@pragmasys.com. Please do not send more than 10-20 log files. The files have been sent. Thanks for the files. The delay is occuring at the loading of the crypto library. Please try my first suggestion, but use a value of 2, instead of 1. If that still has a delay, try turning off FIPS mode on the General Settings page of the Local Server Configuration program and let me know if that fixes the issue.
Changing the registry value to 2 solved the issue. Thank you for all your help.
|
|