Timeline for Windows SSH: Permissions for 'private-key' are too open
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 29 at 17:50 | comment | added | rundekugel | cp to ~ was the trick. without permissions could not be set with chmod | |
| Sep 1, 2021 at 5:03 | comment | added | Param Siddharth | Git-Bash would also do the job straight out-of-the-box. | |
| Apr 20, 2021 at 20:34 | comment | added | Ben Saunders | THANK YOU, this was making me absolutely miserable, you've restored my faith in humanity and made me a better dev | |
| Mar 24, 2021 at 15:07 | comment | added | Dr Potato | At least in Linux and Mac the ssh final part is not necessary, chmod 600 on the ppk file and then sftp connection works. see stackabuse.com/… | |
| Sep 17, 2020 at 14:37 | comment | added | alex |
+1 - this appears to be the working solution for Windows Terminal / WSL1+2 users. I also did a chown for good measure and used sudo ssh and I was able to connect.
|
|
| Aug 31, 2020 at 14:42 | comment | added | Raiden Core | Best answer here. | |
| Feb 22, 2020 at 1:27 | history | edited | Giacomo1968 | CC BY-SA 4.0 |
added 8 characters in body
|
| Sep 6, 2019 at 18:35 | review | Late answers | |||
| Sep 6, 2019 at 19:40 | |||||
| Sep 6, 2019 at 18:20 | review | First posts | |||
| Sep 7, 2019 at 4:12 | |||||
| Sep 6, 2019 at 18:17 | history | answered | JKauffman | CC BY-SA 4.0 |