Kerberos support (cannot log in)?

[GitMensch]

Test setup: two machines, one is RHEL7 (OpenSSH_6.6.1p1), the other CentOS 7.9 (OpenSSH_7.4p1); trying to connect from OpenSSH distributed in Windows (7.7p1) works fine to both machines, both using an explicit user or specifying no user at all; no password needed (using Kerberos authentication).

Connecting from the same machine using this extension works to CentOS 7.9 - but I need to explicit specify the user and enter the password. Connecting to the RHEL7 one does not work at all.

The log says:

[Trace - 10:00:29.566] Identity keys: None [Info - 10:00:29.587] Trying no-auth authentication [Info - 10:00:29.589] Trying password authentication [Error - 10:00:30.25] Error resolving authority Error: All configured authentication methods failed

Questions:

• Is there support for Kerberos so far?
• Currently the ssh connection options (= more than user, host, port) can only be configured by "Open SSH configuration file" - would it be possible to add a GUI for that?

Note: explicit configuring ~/.ssh/config and explicit specifying user and key (via IdentityFile option) leads to a working connection to both servers (previously even the ones that got a password entered on request did [often] connect, but failed to work).

[jeanp413]

Hey @GitMensch

Is there support for Kerberos so far?

No support for Kerbereos sadly, there's an issue about supporting it in ssh2 library but not sure if they plan to add it or not

Currently the ssh connection options (= more than user, host, port) can only be configured by "Open SSH configuration file" - would it be possible to add a GUI for that?

You mean updating .ssh/config file from a command like ssh -i ~/.ssh/mykey user@host so It shows:

Host user@host
    IdentityFile ~/.ssh/mykey

[GitMensch]

You mean updating .ssh/config file from a command

No, I mean a GUI or at least a working "+" which asks for the common parameters via a dialog. But obviously this is a separate issue (this one seems to be "blocked external"). Should I reference it in a new one?

[jeanp413]

Sure create a new issue for that