From af3849eff9bb56a3d2a26f85b89509db40ac7503 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Nicol=C3=A1s=20Reynolds?= Date: Sat, 28 Apr 2012 14:43:31 -0300 Subject: Markdown format --- README.markdown | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) create mode 100644 README.markdown (limited to 'README.markdown') 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 " 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 ;) -- cgit v1.2.3