Renu Fulmali
12/05/2025, 11:38 AMkapa.ai
12/05/2025, 11:38 AMssh-rsa in the connector JVM or in Airbyte’s SSH stack, and they also show that Airbyte is actively moving away from older SSH algorithms rather than adding them. In fact, there is a recent change in the opposite direction: the SFTP source was updated to work with servers that do not support ssh-rsa anymore, by switching away from the old JSch library and fixing “Algorithm negotiation fails” errors. [[source-sftp issue](https://github.com/airbytehq/airbyte/issues/60850)] Given that: - There is no documented connector/JVM flag in the provided docs to re‑enable ssh-rsa. - The trend in the codebase is to modernize algorithms (e.g., fixing incompatibility with servers that dropped ssh-rsa). [[source-sftp issue](https://github.com/airbytehq/airbyte/issues/60850)] I’m not able to point you to a supported configuration knob in Airbyte to turn ssh-rsa back on. Practical options based on the available info: 1. Change the server side to support one of the modern algorithms already proposed by the client (e.g. rsa-sha2-256, rsa-sha2-512, ecdsa-sha2-*, ssh-ed25519), if your security policy allows it. Your error shows the client is offering these, but the server only offers ssh-rsa. 2. Upgrade to the latest connector / Airbyte version in case you’re hitting an older SSH implementation; some connectors have had SSH-related fixes recently (as with source-sftp). [[source-sftp issue](https://github.com/airbytehq/airbyte/issues/60850)] If you manage Airbyte yourself and want to force ssh-rsa at the JVM level, that would require custom code or library changes that are not documented in the provided sources, so I can’t give you a reliable, supported recipe for that.