"SSH-2.0-OpenSSH_for_Windows_9.5' is not recognized as an internal or external command, operable program or batch file. #2252
Comments
|
A temporary workaround is copying the sshd executable ( server ) and naming it "SSH-2.0-OpenSSH_for_Windows_9.5", this particulair error then gets resolved, however it's impossible sshd copies for every client out there, so the underlying issue should still be fixed imho. |
|
Are you still facing this issue? Can provide the full debug logs from both the ssh client and server? |
|
@tgauth to my knowledge I am still having this error. As stated I did find a workaround, that holds up for now, but if I remove those copies of the executable the error comes back. I don't have any server logs at the moment. |
|
hello , PS C:\WINDOWS\system32> cd 'C:\Program Files\OpenSSH' Voulez-vous exécuter le logiciel de cet éditeur non approuvé ? Voulez-vous exécuter le logiciel de cet éditeur non approuvé ? Need to remove the inheritance before repair the rules. 'AUTORITE NT\Utilisateurs authentifiés' should not have access to 'C:\ProgramData\ssh\sshd_config'.. [*] C:\ProgramData\ssh\ssh_host_dsa_key [*] C:\ProgramData\ssh\ssh_host_dsa_key.pub [*] C:\ProgramData\ssh\ssh_host_ecdsa_key [*] C:\ProgramData\ssh\ssh_host_ecdsa_key.pub [*] C:\ProgramData\ssh\ssh_host_ed25519_key [*] C:\ProgramData\ssh\ssh_host_ed25519_key.pub [*] C:\ProgramData\ssh\ssh_host_rsa_key [*] C:\ProgramData\ssh\ssh_host_rsa_key.pub Done. PS C:\Program Files\OpenSSH> .\FixUserFilePermissions.ps1 Voulez-vous exécuter le logiciel de cet éditeur non approuvé ? [*] C:\Users\alexa.ssh\id_rsa [*] C:\Users\alexa.ssh\id_rsa.pub Done. PS C:\Program Files\OpenSSH> ssh alexa@81.49.182.197 Status Name DisplayName Running sshd OpenSSH SSH Server PS C:\Program Files\OpenSSH>" |
|
are there any network or firewall rules preventing inbound traffic on port 22? |
|
i have bit defefender endpoint security tools with exclusion |
|
can you provide the SSHD logs? |
|
i change the path to :"C:\Program Files\OpenSSH" in gravity zone , and i 've nothing in logs where are the logs if it’s not there? |
|
please see https://github.com/PowerShell/Win32-OpenSSH/wiki/Troubleshooting-Steps for info on how to collect the logs |
|
ok , |
|
if you're running you can get the full log with password auth by changing the sshd_config settings mentioned under "Troubleshooting more complex issues" in the above link |
|
vous m'aider pas du tout ,j'ai essayé de modifier le les permission du dossier `PS C:\WINDOWS\system32> sshd.exe -d Need to remove the inheritance before repair the rules. 'AUTORITE NT\Utilisateurs authentifiés' should not have access to 'C:\ProgramData\ssh\sshd_config'.. [*] C:\ProgramData\ssh\ssh_host_dsa_key [*] C:\ProgramData\ssh\ssh_host_dsa_key.pub [*] C:\ProgramData\ssh\ssh_host_ecdsa_key [*] C:\ProgramData\ssh\ssh_host_ecdsa_key.pub [*] C:\ProgramData\ssh\ssh_host_ed25519_key [*] C:\ProgramData\ssh\ssh_host_ed25519_key.pub [*] C:\ProgramData\ssh\ssh_host_rsa_key [*] C:\ProgramData\ssh\ssh_host_rsa_key.pub Done. PS C:\Program Files\OpenSSH> .\FixUserFilePermissions.ps1 [*] C:\Users\alexa.ssh\id_rsa [*] C:\Users\alexa.ssh\id_rsa.pub Done. PS C:\Program Files\OpenSSH> sshd.exe -d purquoi ne peut on pas utiliser le fichier sshd_config_default dans le dossier du package openssh server 9.x.y ? And, please, stop voting left -_-" ... |
|
sons of bitches have fun sending a powershell malware in the appData/ Roaming folder after seeing my ip, I hope it’s not you because if 'there are prosecutions , there are some who will get their asses hurt! |
|
I can connect in localhost to the sshd server , but not from my active domain durectory that I do not know, here is my attempt to install active directory on a windows 10 client : |
|
@tgauth did you guys have a look at the issue I have documented? |
|
i 've this :``` |
|
i don't know where is the problem , |
|
and logs contains : ``` |
Prerequisites
Steps to reproduce
I updated openssh installations on a machine running sshd through winget because they were quite dated. Unfortunately, I could only find the beta releases. When connecting to the machine it gives out the following error "'SSH-2.0-OpenSSH_for_Windows_9.5' is not recognized as an internal or external command, operable program or batch file."
To work around the issue on the server, I've just copied over the sshd executable and renamed it 'SSH-2.0-OpenSSH_for_Windows_9.5'. This supringsinly works well, but when connecting from other clients like the one bundled with git setup it'll complain about other variants of executables missing e.g. "'SSH-2.0-OpenSSH_9.7' is not recognized as an internal or external command, operable program or batch file."
On surface, it seems that when connecting to sshd, the ssh version the user uses relays some information about client version used and the sshd(eamon) uses that to fork the process.
Expected behavior
ssh connects without disconnecting due to missing executable based on client versiionActual behavior
Error details
n/aEnvironment data
n/aVersion
This problem seems to happen for both ssh bundled in git, and the one installed from this repository.
SSH-2.0-OpenSSH_for_Windows_9.5 <--> SSH-2.0-OpenSSH_for_Windows_9.5
SSH-2.0-OpenSSH_9.7 <--> SSH-2.0-OpenSSH_for_Windows_9.5
Visuals
n/a
The text was updated successfully, but these errors were encountered: