Re:Why does my SSH private key still work after changing som...
by InvaderFizz on Saturday December 31, 2022 @11:32AM
(#34197978)
> Thanks for the clarification, but from the end user's perspective it's all the same in the end?
The vast majority of users will not experience this unless their client is old. I literally dealt with this issue yesterday with one of our lead Developers.
He was using JSch in an older version of dbeaver, couldn't SSH into the new test environments we're validating on Ubuntu 22.04. Turns out to be this exact issue. The solution was to update dbeaver and switch to the new default SSHJ client within it.
Same private key, new client. Problem solved.
I will be using this as leverage to force a company standard change from RSA4096 keys to ed25519. So I am not going to clarify the difference to the Security teams.
The vast majority of users will not experience this unless their client is old. I literally dealt with this issue yesterday with one of our lead Developers.
He was using JSch in an older version of dbeaver, couldn't SSH into the new test environments we're validating on Ubuntu 22.04. Turns out to be this exact issue. The solution was to update dbeaver and switch to the new default SSHJ client within it.
Same private key, new client. Problem solved.
I will be using this as leverage to force a company standard change from RSA4096 keys to ed25519. So I am not going to clarify the difference to the Security teams.