Closed pcgeek86 closed 1 year ago
It should have already been fixed in 0.10. Duplicated of #123
Sorry I missed that one.
@veeso it somehow isn´t fixed for me even though i'm on the latest version, it keeps on asking me my password
2022-11-04T14:43:53.400022129Z [INFO] Client is not connected to remote; connecting to something.something.something.fr:4222
2022-11-04T14:43:53.473244033Z [ERROR] Authentication failed: [Session(-18)] Authentication failed (username/password)
2022-11-04T14:43:54.433694461Z [INFO] FileTransferActivity terminated due to 'Authentication'
It should have already been fixed in 0.10. Duplicated of #123
I don't understand......
I can ssh to an host using my default id_rsa key like this:
But, it failed on termscp, it said "bad address syntax":
(termscp sftp://test-ubuntu
failed too)
However, I did set the ssh config path:
By the way, may I request a new feature, like key remapping? I prefer vim-like keymap.
I have the same issue, same repro, though a different error message.
My ssh config has more than host info in it - for example Protocol 2
at the top. This gives an error IO error (Could not parse configuration file: unknown field: Protocol)
.
Then, if I comment out everything in my config except the Host blocks and retry an scp connection with no user/pass, I get a different error: authentication failed (could not find any suitable RSA key to authenticate with)
.
(My ssh host does not permit key/pass entry, only ssh, so I'm unable to use termscp to connect because of this problem.)
definitely fixed in 0.11
Did v0.11.0 solve your problem? It does not work for me.
Yes, 0.11.0 fixed this. At this point if it still doesn't work for you, please open another issue reporting your ssh configuration and the host parameters.
Description
I would like
termscp
to use theid_rsa
default SSH private key on my local filesystem.Steps to reproduce
Try to connect to SFTP or SCP endpoint without using a password. Authentication fails.
Expected behaviour
By default,
termscp
should use$HOME/.ssh/id_rsa
to authenticate as<username>
at<hostname>
.Environment
Log
Report the snippet of the log file containing the unexpected behaviour. If there is any information you consider to be confidential, shadow it.
Additional information
Add any other context about the problem here.