Timeline for Windows SSH: Permissions for 'private-key' are too open
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 24, 2022 at 9:37 | comment | added | rundekugel | results in: -r--r--r-- 1 xxx xxx xxx xxxxxxxx id_rsa but we want -rwx------ | |
| Aug 20, 2021 at 2:09 | comment | added | Jeremy Hajek | a Non-administrator cmd.exe prompt | |
| Aug 15, 2021 at 7:03 | comment | added | Matthew Lock | doesn't worth either, still gives "Permissions for '' are too open." | |
| Aug 27, 2020 at 20:18 | comment | added | Jim Fischer | NB: These commands must be issued within a command window (CMD.EXE). The second command line would not work for me in a PowerShell command window; it would produce an error message saying 'Invalid parameter "%username%"', even though the environment variable USERNAME is defined an has the correct value. Also, after I invoked these two icacls commands on my RSA private key file, I continue to get the "bad permissions" error message when I invoke ssh in a PowerShell window. | |
| S Oct 4, 2019 at 13:45 | review | Low quality posts | |||
| Oct 4, 2019 at 18:15 | |||||
| S Oct 4, 2019 at 13:45 | review | Late answers | |||
| Oct 4, 2019 at 13:53 | |||||
| Oct 4, 2019 at 13:30 | review | First posts | |||
| Oct 4, 2019 at 18:15 | |||||
| Oct 4, 2019 at 13:28 | history | answered | Walter Ferrao | CC BY-SA 4.0 |