- Outdated SSH Software: Ensure that you're running the latest version of the SSH software on your system. Older versions might not support the newer encryption algorithms required by the server.
- Server Configuration: The issue might be related to the server-side configuration. Some servers might have updated their security policies to disallow certain encryption algorithms or key types. You can verify this by checking the server's SSH configuration and its supported encryption algorithms.
- Client Configuration: On the client side, ensure that your SSH configuration is set up correctly and that it supports the encryption methods accepted by the server.
- Corrupt or Unsupported Keys: It's possible that the keys are corrupt or not supported. You mentioned trying both RSA and ed25519 keys; make sure they are generated correctly and are not corrupted. RSA keys should generally be at least 2048 bits in length due to newer security standards.
- Firewall or Network Issues or Anitivirus: Sometimes, network or firewall or antivirus settings can interfere with SSH key exchange. Ensure that there are no such barriers affecting the communication between your client and the server.
- Libraries and Dependencies: If you are using a library or tool that depends on underlying SSH libraries (like libgit2), there could be issues with the library itself that might require an update or a workaround. For instance, some users have found that using the command line instead of a GUI can circumvent issues if the GUI application is not properly handling SSH key exchanges.
- Technical Services and Consulting
- Embedded Systems | Firmware Developement | Simulations
- Electrical and Electronics Engineering