diff options
| author | Nicolás Reynolds <fauno@kiwwwi.com.ar> | 2012-04-28 14:43:31 -0300 |
|---|---|---|
| committer | Nicolás Reynolds <fauno@kiwwwi.com.ar> | 2012-04-28 14:43:31 -0300 |
| commit | af3849eff9bb56a3d2a26f85b89509db40ac7503 (patch) | |
| tree | 2f6f8050038b8585fcb620c8bc0ee925c561f9ed /README.markdown | |
| parent | 07859847f55c364a022e8e08ec8a17c1326f1dd1 (diff) | |
Markdown format
Diffstat (limited to 'README.markdown')
| -rw-r--r-- | README.markdown | 22 |
1 files changed, 22 insertions, 0 deletions
diff --git a/README.markdown b/README.markdown new file mode 100644 index 0000000..b50140f --- /dev/null +++ b/README.markdown @@ -0,0 +1,22 @@ +Parabola Hackers +================ + +## How to add new keys + +* Add your key to the authorized_keys file. +* Change the key comment to the "Name <name@email.nu>" format (just for keeping + it tidy) +* Commit +* Push if you have push privileges and you're adding a new hacker, or +* Run `git format-patch HEAD-1` and send the generated patches to Parabola + +## How does this work? + +There's a post-receive hook on the origin hackers.git repository that updates +a clone on ~/.ssh. Any change pushed to it is immediately reflected in access +privileges for the git user. + +## Is this unsecure? + +'git' is an unprivileged user. If you know how to skip this and gain access to +our servers be kind and let us now ;) |