[windows11] ssh-agent onthoud wachtwoord niet

[Simkin]

EDIT: Opgelost! Het is ESSENTIEEL dat je OOK de .pub key in de .ssh dir bewaard! Anders blijft de agent om een ww vragen

----


Ik draai zonder problemen de ssh-agent op mijn laptop maar na een nieuwe windows installatie heb ik problemen op mijn desktop: het wachtwoord van mijn private key wordt niet onthouden en ik snap niet waarom.

code:

PS D:\> Get-Service ssh-agent

Status   Name               DisplayName
------   ----               -----------
Running  ssh-agent          OpenSSH Authentication Agent


PS D:\> ssh-add -l
2048 SHA256:xxxxx C:\Users\lmole\.ssh\openssh1.key (RSA)
2048 SHA256:xxxxx C:\Users\lmole/.ssh/id_rsa (RSA)

code:

PS D:\> ssh jumpserver
Enter passphrase for key 'C:\Users\lmole/.ssh/id_rsa':

code:

PS D:\> ssh -v jumpserver
OpenSSH_for_Windows_8.6p1, LibreSSL 3.4.3
debug1: Reading configuration data C:\\Users\\lmole/.ssh/config
debug1: C:\\Users\\lmole/.ssh/config line 1: Applying options for *
debug1: C:\\Users\\lmole/.ssh/config line 54: Applying options for jumpserver
debug1: Authenticator provider $SSH_SK_PROVIDER did not resolve; disabling
debug1: Connecting to 100.xxx.xxx.xxx [100.xxx.xxx.xxx] port 22.
debug1: Connection established.
debug1: identity file C:\\Users\\lmole/.ssh/id_rsa type -1
debug1: identity file C:\\Users\\lmole/.ssh/id_rsa-cert type -1
debug1: identity file C:\\Users\\lmole/.ssh/id_dsa type -1
debug1: identity file C:\\Users\\lmole/.ssh/id_dsa-cert type -1
debug1: identity file C:\\Users\\lmole/.ssh/id_ecdsa type -1
debug1: identity file C:\\Users\\lmole/.ssh/id_ecdsa-cert type -1
debug1: identity file C:\\Users\\lmole/.ssh/id_ecdsa_sk type -1
debug1: identity file C:\\Users\\lmole/.ssh/id_ecdsa_sk-cert type -1
debug1: identity file C:\\Users\\lmole/.ssh/id_ed25519 type -1
debug1: identity file C:\\Users\\lmole/.ssh/id_ed25519-cert type -1
debug1: identity file C:\\Users\\lmole/.ssh/id_ed25519_sk type -1
debug1: identity file C:\\Users\\lmole/.ssh/id_ed25519_sk-cert type -1
debug1: identity file C:\\Users\\lmole/.ssh/id_xmss type -1
debug1: identity file C:\\Users\\lmole/.ssh/id_xmss-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_7.4
debug1: compat_banner: match: OpenSSH_7.4 pat OpenSSH_7.0*,OpenSSH_7.1*,OpenSSH_7.2*,OpenSSH_7.3*,OpenSSH_7.4*,OpenSSH_7.5*,OpenSSH_7.6*,OpenSSH_7.7* compat 0x04000002
debug1: Authenticating to 100.xxx.xxx.xxx:22 as 'lmole'
debug1: load_hostkeys: fopen C:\\Users\\lmole/.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: [e-mail] MAC: <implicit> compression: none
debug1: kex: client->server cipher: [e-mail] 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:N9yNbxxxx
debug1: load_hostkeys: fopen C:\\Users\\lmole/.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 '100.xxx.xxx.xxx' is known and matches the ED25519 host key.
debug1: Found key in C:\\Users\\lmole/.ssh/known_hosts:8
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: Will attempt key: C:\\Users\\lmole/.ssh/id_rsa
debug1: Will attempt key: C:\\Users\\lmole/.ssh/id_dsa
debug1: Will attempt key: C:\\Users\\lmole/.ssh/id_ecdsa
debug1: Will attempt key: C:\\Users\\lmole/.ssh/id_ecdsa_sk
debug1: Will attempt key: C:\\Users\\lmole/.ssh/id_ed25519
debug1: Will attempt key: C:\\Users\\lmole/.ssh/id_ed25519_sk
debug1: Will attempt key: C:\\Users\\lmole/.ssh/id_xmss
debug1: SSH2_MSG_EXT_INFO received
debug1: kex_input_ext_info: server-sig-algs=<rsa-sha2-256,rsa-sha2-512>
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password,keyboard-interactive
debug1: Next authentication method: publickey
debug1: Trying private key: C:\\Users\\lmole/.ssh/id_rsa
Enter passphrase for key 'C:\Users\lmole/.ssh/id_rsa':
debug1: identity added to agent: C:\\Users\\lmole/.ssh/id_rsa
debug1: Authentication succeeded (publickey).
Authenticated to 100.xxx.xxx.xxx ([100.xxx.xxx.xxx]:22).
debug1: Local connections to LOCALHOST:9999 forwarded to remote address 172.xxx.xxx.xxx:22
debug1: Local forwarding listening on ::1 port 9999.
debug1: channel 0: new [port listener]
debug1: Local forwarding listening on 127.0.0.1 port 9999.
debug1: channel 1: new [port listener]
debug1: channel 2: new [client-session]
debug1: Requesting [e-mail]
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 [e-mail] want_reply 0
debug1: client_input_hostkeys: searching C:\\Users\\lmole/.ssh/known_hosts for 100.xxx.xxx.xxx / (none)
debug1: client_input_hostkeys: searching C:\\Users\\lmole/.ssh/known_hosts2 for 100.xxx.xxx.xxx / (none)
debug1: client_input_hostkeys: hostkeys file C:\\Users\\lmole/.ssh/known_hosts2 does not exist
debug1: client_input_hostkeys: no new or deprecated keys from server
Last login: Wed Feb 15 09:04:43 2023 from 172.xxx.xxx.xxx

De key is toegevoegd aan de agent maar elke keer weer prompt hij voor het wachtwoord, waarna ik netjes wordt ingelogd.

Kan iemand mij op weg helpen?

[Hero of Time]

Dit zal toch echt met de Windows versie van SSH client te maken hebben. Je vraag, met als OS Windows 11, heeft daarom niets te zoeken in Linux en Overige Clients.

Ik verplaats je topic dan ook naar Windows Clients. LNX -> WOS.

[straaljager27]

2 dingen: klinkt alsof je een passphrase op je key hebt, die niet herkend/ingevoerd/bekend is. Lees eens deze links:
https://docs.github.com/e...-with-ssh-key-passphrases
en oplossing: https://superuser.com/que...hen-im-doing-ssh-operatio

Alternatief: check eens hoe je ntfs rechten op de .keyfile staan. Ik zie wel eens rare dingen gebeuren als er meer dan 3 ACL's op staan. Zou enkel Admin,System, en de betreffende user moeten zijn