authentication: adding hostname parameter to ssh method

[danlavu]

Some tests will require to connect using the client hostname instead of localhost, adding this flexibility.

[danlavu]

INFO     2024-12-20 07:03:42,965          client.test Previous command completed with exit code 202
                                                      Output: |
                                                        spawn ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o PreferredAuthentications=password -o NumberOfPasswordPrompts=1 -l user1 localhost
                                                        KnownHostsCommand-ORDER /usr/bin/sss_ssh_knownhosts localhost failed, status 1

                                                        KnownHostsCommand failed

Ran into the following issue, SSSD/sssd#7664 , I'm sure the host is not up to date, but it bring this to my attention.

[ikerexxe]

mmm let me see if I understand it correctly. If we assume a topology with 2 clients and an LDAP-like server. Currently we are only able to ssh to localhost, thus client1 can only ssh to client1 and client2 to client2. You want to use this feature to be able to ssh from client1 to client2 (or some other host). Am I right?

[jakub-vavra-cz]

mmm let me see if I understand it correctly. If we assume a topology with 2 clients and an LDAP-like server. Currently we are only able to ssh to localhost, thus client1 can only ssh to client1 and client2 to client2. You want to use this feature to be able to ssh from client1 to client2 (or some other host). Am I right?

My guess is that You can both login from/to different machine and also run ssh with hostname needing dns resolution first or supply ip address making it more flexible instead of harcoded ssh to localhost.

[jakub-vavra-cz]

LGTM.