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 | |
|---|---|---|---|---|---|
| Nov 21, 2022 at 15:53 | vote | accept | Melly Donald | ||
| Nov 15, 2022 at 10:01 | answer | added | Daniel B | timeline score: 2 | |
| Nov 15, 2022 at 8:52 | comment | added | Daniel B | I fixed your text quote from the screenshot. It is very important to use the correct terms. Public and private key are different things with very different secrecy requirements. // The permissions you set on Windows are (mostly) irrelevant when mounted in a Docker container. They are not fully mapped to Linux octal permissions. | |
| Nov 15, 2022 at 8:48 | history | edited | Daniel B | CC BY-SA 4.0 |
Fix quote from screenshot, minor improvements
|
| Nov 15, 2022 at 8:28 | comment | added | Melly Donald | Thank your for answering. What do you mean by the permissions in the container? How can I edit this? | |
| Nov 15, 2022 at 8:27 | history | edited | Melly Donald | CC BY-SA 4.0 |
added 668 characters in body
|
| Nov 14, 2022 at 22:29 | comment | added | heavyd | It looks like you're trying to run ssh from inside a container, is that correct? You would need to make sure the permissions inside the container are correct, not in your Windows host. | |
| Nov 14, 2022 at 22:26 | history | edited | heavyd | CC BY-SA 4.0 |
deleted 6 characters in body
|
| S Nov 14, 2022 at 22:20 | review | First questions | |||
| Nov 14, 2022 at 22:53 | |||||
| S Nov 14, 2022 at 22:20 | history | asked | Melly Donald | CC BY-SA 4.0 |