Timeline for Cannot use "ecdsa" and "rsa" in parallel when using SFTP
Current License: CC BY-SA 4.0
6 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Dec 15, 2022 at 16:30 | comment | added | becke-ch |
I did not invest too much time in my test code but thx for the hint. I've put in on the agenda for next release/cleanup to implement separate known_hosts files for the different tests.
|
|
Dec 14, 2022 at 21:49 | comment | added | Gilles 'SO- stop being evil' |
@becke-ch Ok, but why are you sharing known_hosts between tests? It looks like your test environment is not properly isolated.
|
|
Dec 14, 2022 at 19:50 | comment | added | becke-ch | (I'm using the OpenSSH SFTP Server Client for automated integration testing of my Android Java based SFTP Server implementation and in this context testing the different public key algorithms) | |
Dec 14, 2022 at 12:23 | comment | added | Gilles 'SO- stop being evil' | @becke-ch It's not just a matter of “accept the user decision”. The client program has no way to know that the two keys are for the same machine. What you're doing is very unusual (and I don't understand why you're doing it, you seem to be making your life more complicated for no benefit). | |
Dec 14, 2022 at 12:17 | comment | added | becke-ch |
Thx for the reply. I still think the ssh client should just give a warning but accept the user decision to support different algos for the same server in parallel. Maybe you can add the following workaround/solution to your reply: "When forcing the ssh client not to use the default public key algorithm then you should as well force the client not to use the default known_hosts file e.g.: sftp -v -o HostKeyAlgorithms=ecdsa-sha2-nistp256 test--s0-v1@localhost " sftp -v -o HostKeyAlgorithms=ecdsa-sha2-nistp256 -o UserKnownHostsFile=~/.ssh/known_hosts_ecdsa test--s0-v1@localhost`
|
|
Dec 12, 2022 at 20:40 | history | answered | Gilles 'SO- stop being evil' | CC BY-SA 4.0 |