diff options
| author | Chris Rebert <github@rebertia.com> | 2014-12-09 22:43:36 +0300 |
|---|---|---|
| committer | Chris Rebert <github@rebertia.com> | 2014-12-09 22:43:36 +0300 |
| commit | 5298128da96b6e5c0020593b0478fb8ff43a12a8 (patch) | |
| tree | 724ed4754f4993916985a053847a495b2bf3718b | |
| parent | 1c9ffdc208de9bc6b61530431b3a01db1b5c2397 (diff) | |
erm, known_hosts, not authorized_hosts
| -rw-r--r-- | README.md | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -52,7 +52,7 @@ Savage accepts exactly one optional command-line argument, which is the port num When running Savage, its working directory needs to be a non-bare git repo which is a clone of the repo being monitored. -The Unix user that Savage runs as needs to have an SSH key setup, and that SSH key needs to be registered in Savage's GitHub user account, so that Savage can pull-to/push-from GitHub securely via SSH. GitHub's public key also needs to be present in the `authorized_hosts` of Savage's Unix user. +The Unix user that Savage runs as needs to have an SSH key setup, and that SSH key needs to be registered in Savage's GitHub user account, so that Savage can pull-to/push-from GitHub securely via SSH. GitHub's public key also needs to be present in the `known_hosts` of Savage's Unix user. If you're using Sauce, we recommend [using a sub-account](https://saucelabs.com/sub-accounts) for Savage, to completely prevent any possibility of compromise of your main account. |