2 ms·

Thanks for trying it out and describing your issue. I assume that you mean that you have the IdentityFile option configured for every connection in your config

Thanks for trying it out and describing your issue. I assume that you mean that you have the IdentityFile option configured for every connection in your config file? That should work though, it might not list the file as an explicit detected key-based authentication method when you edit the connection (Might be listed as None), but it should still apply the identity file option you have set in the config. If that is not happening, then this is a bug and I can investigate that.

eigenvalue 2y ago
Yes each entry in the ssh config file has its own IdentityFile entry with the full path to the key file. Maybe it’s because they are indented an additional level more than the HostName and User fields it’s not recognizing them?
- crschnick 2y ago
  The indentation shouldn't really matter, I will try to figure out what went wrong there.
- crschnick 2y ago
  So I released an update that should hopefully fix / tweak this behavior. I think to apply you would need to remove the config entry in xpipe and search for it again.
  - eigenvalue 2y ago
    Thanks, will try it and let you know!
  - eigenvalue 2y ago
    I updated but see no way to make it re-import the config file. Sorry to say, but I'm finding the whole thing very confusing and counter-intuitive. It should automatically import the .ssh config file when you start it up.
    - crschnick 2y ago
      Alright that is good feedback. I haven't actually thought about this, but it would also make sense when a user updates their config hosts in general. There is a refresh button for the config, but that one also does not reload everything. I will definitely improve that. About the reimport, you can right-click the SSH config root, remove it, click on the magnifying glass button on the local machine to automatically add it again with the latest info. But I can fully understand that you don't want to do that, dealing with unintuitive interfaces isn't fun.

eigenvalue 2y ago

Yes each entry in the ssh config file has its own IdentityFile entry with the full path to the key file. Maybe it’s because they are indented an additional level more than the HostName and User fields it’s not recognizing them?

crschnick 2y ago
The indentation shouldn't really matter, I will try to figure out what went wrong there.
crschnick 2y ago
So I released an update that should hopefully fix / tweak this behavior. I think to apply you would need to remove the config entry in xpipe and search for it again.
- eigenvalue 2y ago
  Thanks, will try it and let you know!
- eigenvalue 2y ago
  I updated but see no way to make it re-import the config file. Sorry to say, but I'm finding the whole thing very confusing and counter-intuitive. It should automatically import the .ssh config file when you start it up.
  - crschnick 2y ago
    Alright that is good feedback. I haven't actually thought about this, but it would also make sense when a user updates their config hosts in general. There is a refresh button for the config, but that one also does not reload everything. I will definitely improve that. About the reimport, you can right-click the SSH config root, remove it, click on the magnifying glass button on the local machine to automatically add it again with the latest info. But I can fully understand that you don't want to do that, dealing with unintuitive interfaces isn't fun.