Timeline for Should the key for an automatically running cron job that runs over ssh not have a passphrase?
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Mar 17, 2019 at 10:19 | history | suggested | Dae | CC BY-SA 4.0 |
fix typo in authorized_keys
|
| Mar 17, 2019 at 8:06 | review | Suggested edits | |||
| S Mar 17, 2019 at 10:19 | |||||
| Jul 9, 2015 at 0:54 | vote | accept | leeand00 | ||
| Jul 7, 2015 at 13:10 | history | edited | Celada | CC BY-SA 3.0 |
added 413 characters in body
|
| Jul 7, 2015 at 12:37 | comment | added | Jenny D |
In addition to the things you've already mentioned, I'd recommend also limiting where the key can connect from. You do this by adding from=ipaddress.or.hostname at the start of the key, together with the command.
|
|
| Jul 7, 2015 at 2:51 | history | edited | Celada | CC BY-SA 3.0 |
added 49 characters in body
|
| Jul 7, 2015 at 2:42 | history | answered | Celada | CC BY-SA 3.0 |