ssh 输出中此行的含义是什么:“身份验证器提供程序 $SSH_SK_PROVIDER 未解析;正在禁用”?

ssh 输出中此行的含义是什么:“身份验证器提供程序 $SSH_SK_PROVIDER 未解析;正在禁用”?

一切正常,ssh 使用私钥-公钥对进行连接。输出
中只有几项内容ssh -v Ora2对我来说不清楚。

这是完整的ssh -v Ora2输出:

PS C:\Users\roeslermichal> ssh -v Ora2
OpenSSH_for_Windows_8.6p1, LibreSSL 3.4.3
debug1: Reading configuration data C:\\Users\\roeslermichal/.ssh/config
debug1: C:\\Users\\roeslermichal/.ssh/config line 19: Applying options for Ora2
debug1: Authenticator provider $SSH_SK_PROVIDER did not resolve; disabling
debug1: Connecting to 10.32.81.218 [10.32.81.218] port 22.
debug1: Connection established.
debug1: identity file C:\\Users\\roeslermichal\\.ssh\\poczt_id_ed25519 type 3
debug1: identity file C:\\Users\\roeslermichal\\.ssh\\poczt_id_ed25519-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_for_Windows_8.6
debug1: Remote protocol version 2.0, remote software version OpenSSH_8.0
debug1: compat_banner: match: OpenSSH_8.0 pat OpenSSH* compat 0x04000000
debug1: Authenticating to 10.32.81.218:22 as 'michal'
debug1: load_hostkeys: fopen C:\\Users\\roeslermichal/.ssh/known_hosts2: No such file or directory
debug1: load_hostkeys: fopen __PROGRAMDATA__\\ssh/ssh_known_hosts: No such file or directory
debug1: load_hostkeys: fopen __PROGRAMDATA__\\ssh/ssh_known_hosts2: No such file or directory
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: algorithm: curve25519-sha256
debug1: kex: host key algorithm: ssh-ed25519
debug1: kex: server->client cipher: [email protected] MAC: <implicit> compression: none
debug1: kex: client->server cipher: [email protected] MAC: <implicit> compression: none
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: SSH2_MSG_KEX_ECDH_REPLY received
debug1: Server host key: ssh-ed25519 SHA256:jQ2i6lqzzZnhdPc+GKQCS6iiCD5W/2wDzhLvigIlytg
debug1: load_hostkeys: fopen C:\\Users\\roeslermichal/.ssh/known_hosts2: No such file or directory
debug1: load_hostkeys: fopen __PROGRAMDATA__\\ssh/ssh_known_hosts: No such file or directory
debug1: load_hostkeys: fopen __PROGRAMDATA__\\ssh/ssh_known_hosts2: No such file or directory
debug1: Host '10.32.81.218' is known and matches the ED25519 host key.
debug1: Found key in C:\\Users\\roeslermichal/.ssh/known_hosts:10
debug1: rekey out after 134217728 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: rekey in after 134217728 blocks
debug1: pubkey_prepare: ssh_get_authentication_socket: No such file or directory
debug1: Will attempt key: C:\\Users\\roeslermichal\\.ssh\\poczt_id_ed25519 ED25519 SHA256:eQBpsX9pvzP6RuorzRWhlK2s4sOEdj3KrgME3TGeSMU explicit
debug1: SSH2_MSG_EXT_INFO received
debug1: kex_input_ext_info: server-sig-algs=<ssh-ed25519,ssh-rsa,rsa-sha2-256,rsa-sha2-512,ssh-dss,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521>
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey
debug1: Next authentication method: publickey
debug1: Offering public key: C:\\Users\\roeslermichal\\.ssh\\poczt_id_ed25519 ED25519 SHA256:eQBpsX9pvzP6RuorzRWhlK2s4sOEdj3KrgME3TGeSMU explicit
debug1: Server accepts key: C:\\Users\\roeslermichal\\.ssh\\poczt_id_ed25519 ED25519 SHA256:eQBpsX9pvzP6RuorzRWhlK2s4sOEdj3KrgME3TGeSMU explicit
debug1: Authentication succeeded (publickey).
Authenticated to 10.32.81.218 ([10.32.81.218]:22).
debug1: channel 0: new [client-session]
debug1: Requesting [email protected]
debug1: Entering interactive session.
debug1: pledge: filesystem full
debug1: ENABLE_VIRTUAL_TERMINAL_INPUT is supported. Reading the VTSequence from console
debug1: ENABLE_VIRTUAL_TERMINAL_PROCESSING is supported. Console supports the ansi parsing
debug1: client_input_global_request: rtype [email protected] want_reply 0
debug1: client_input_hostkeys: searching C:\\Users\\roeslermichal/.ssh/known_hosts for 10.32.81.218 / (none)
debug1: client_input_hostkeys: searching C:\\Users\\roeslermichal/.ssh/known_hosts2 for 10.32.81.218 / (none)
debug1: client_input_hostkeys: hostkeys file C:\\Users\\roeslermichal/.ssh/known_hosts2 does not exist
debug1: client_input_hostkeys: no new or deprecated keys from server
debug1: Remote: /home/michal/.ssh/authorized_keys:1: key options: agent-forwarding port-forwarding pty user-rc x11-forwarding
debug1: Remote: /home/michal/.ssh/authorized_keys:1: key options: agent-forwarding port-forwarding pty user-rc x11-forwarding
Activate the web console with: systemctl enable --now cockpit.socket

我理解其中的大部分内容,但有几行需要解释。

  1. Authenticator provider $SSH_SK_PROVIDER did not resolve; disabling
    我不明白$SSH_SK_PROVIDER目前是什么,什么还没有解决。
    什么被禁用了?
    我的意思是,ssh 刚刚从我的 Windows 11 笔记本电脑读取了 ssh 配置文件并应用了Ora2设置。
    它甚至还没有连接,所以我们在这个过程的早期谈论的是什么身份验证。是
    什么$SSH_SK_PROVIDER
  2. 请为我解释一下这两行:
    SSH2_MSG_KEXINIT 已发送
    SSH2_MSG_KEXINIT 已接收
    我不知道SSH2_MSG_KEXINIT是什么?
    有必要吗?
    我只是使用私钥-公钥对认证。
    我可以关闭吗SSH2_MSG_KEXINIT??

相关内容