summaryrefslogtreecommitdiff
path: root/README.markdown
diff options
context:
space:
mode:
Diffstat (limited to 'README.markdown')
-rw-r--r--README.markdown27
1 files changed, 27 insertions, 0 deletions
diff --git a/README.markdown b/README.markdown
new file mode 100644
index 0000000..de5eee6
--- /dev/null
+++ b/README.markdown
@@ -0,0 +1,27 @@
+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 insecure?
+
+'git' is an unprivileged user. If you know how to skip this and gain access to
+our servers be kind and let us now ;)
+
+## Why?
+
+Gitosis broke once and was never fixed. We didn't need gitosis' granular
+permissions anyway. Now Parabola hackers can add new hackers!