Timeline for Windows SSH: Permissions for 'private-key' are too open
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 29, 2020 at 12:57 | comment | added | JW0914 | The error message is due to using an invalid key format [a PuTTY key], as OpenSSH doesn't support PuTTY keys (they must be converted first via PuTTYgen → Conversions) | |
| Jun 29, 2020 at 12:53 | history | edited | JW0914 | CC BY-SA 4.0 |
Grammatical corrections (incl. formatting)
|
| Nov 12, 2019 at 9:12 | comment | added | smartins | This "fixed" it for me, using C:\Program Files\Git\usr\bin\ssh.exe works as C:\Windows\System32\OpenSSH\ssh.exe does not | |
| May 23, 2019 at 16:45 | comment | added | Shukri Adams | This was also the fix for me. It seems Windows 10 Pro now bundles a pooched version of openssh. I was forced to remove the C:\Windows\System32\OpenSSH folder and add git's ssh.exe to PATH. | |
| Mar 7, 2019 at 0:27 | comment | added | guychouk | This is what helped me, I never got the windows ssh version to work in this scenario, only Git's :( | |
| Jul 9, 2018 at 19:40 | comment | added | JW0914 |
OpenSSH should not be installed to the Windows directory for whole host of reasons, from security, to it being a massive inconvenience should one need to fix a corrupted Windows directory either via DISM or using the Reset option (which has been improved to utilize the WinSxS directory versus reverting to the original install.esd).
|
|
| Apr 5, 2018 at 11:53 | history | answered | Rich S | CC BY-SA 3.0 |