Timeline for SSH Key Permissions chmod settings?
Current License: CC BY-SA 3.0
14 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 2, 2021 at 3:09 | comment | added | woodvi | chmod 644 ~/.ssh/known_hosts If known_hosts is deleted the system will generate a new empty one with the correct permissions. | |
| Jun 28, 2020 at 19:02 | comment | added | Scrooge McDuck | I have reposted a barebone version of my edit to make it different enough from yours to avoid this controversy. | |
| Jun 28, 2020 at 18:32 | comment | added | Scrooge McDuck | Since it clearly seem to me that we can't reach a compromise about this answer's syntax highlighting, inline code positioning and general information context, I simply demand to have my edit posted as a separate answer, like it has already been for 9 months. I am sure in due time consensus through further improvements will be reached. | |
| Jun 28, 2020 at 18:24 | comment | added | Scrooge McDuck | I don't want to convince you that my edit is more readable, I just want it shown somewhere on this page because I find it more readable. About chmod, I believe in this situation some context is needed. | |
| Jun 28, 2020 at 17:45 | comment | added | Gilles 'SO- stop being evil' | @ScroogeMcDuck I find your version hard to understand. You removed part of the explanations, leaving some code snippets with no clear meaning. Making the code snippets multiline doesn't make them more readable. The explanation of the chmod commands is superfluous: explaining chmod is very far from the topic of the question. | |
| Jun 28, 2020 at 4:35 | comment | added | Scrooge McDuck | @fpmurphy: in fact when I was told at first (9 months ago) that my edit was too far away from the original, I reposted as a separate answer. On readability I personally refer to voters' judgement; in due time we can have a fair verdict on that. Of course, to me the 3 upvotes and the in-person considerations it received confirm that already. | |
| Jun 28, 2020 at 4:22 | comment | added | Scrooge McDuck | That said, I just want my answer to be shown for very practical reasons: people ask me how to enable ssh all the time and they find very annoying to copy-paste the many inline commands from Gilles' answer, which among other things they usually find difficult to understand and remember. I don't care if you consider it an improved version of this answer or a completely new one, I only care for people I redirect here (myself included) to have their question answered in the most efficient way. | |
| Jun 28, 2020 at 4:12 | comment | added | Scrooge McDuck | @G-ManSays'ReinstateMonica' I find silly to state that my edit does not improve readibility; if not so, papers would only contain inline equations. On other side I can't understand how an extremely simple and properly highlighted table explaining how to read those chmod can be said superfluous; if that's the case, then why posting commands in the first place and just not point users to bash scripts all the times. | |
| Jun 23, 2020 at 1:59 | comment | added | G-Man Says 'Reinstate Monica' | @terdon: So, are you saying that we should have accepted Scrooge McDuck’s suggested edit? And that Gilles should override us and accept it? (Note that it contains an error.) | |
| Jun 20, 2020 at 19:01 | review | Suggested edits | |||
| Jun 20, 2020 at 22:03 | |||||
| Oct 31, 2019 at 20:31 | review | Suggested edits | |||
| Oct 31, 2019 at 21:57 | |||||
| May 30, 2018 at 18:30 | comment | added | hoelk | I want to add to the answers above that for me my home directory (~/) also needed to have the permissions 755, regardless of the permissions of ~/.ssh and the files therein. (This was on a Synology NAS, might not apply to all linuxes) | |
| Jan 24, 2018 at 16:24 | comment | added | Sooth | What do the permissions on the ~/.ssh/known_hosts need to be? | |
| Jan 25, 2016 at 23:39 | history | answered | Gilles 'SO- stop being evil' | CC BY-SA 3.0 |