From 61fc766d07e5252b9618c6548ea714649ab54a54 Mon Sep 17 00:00:00 2001
From: Luke Shumaker <lukeshu@sbcglobal.net>
Date: Wed, 15 Jun 2016 13:03:50 -0400
Subject: Pull tool configuration into a hackers-git.yml

---
 hackers-git.yml | 35 +++++++++++++++++++++++++++++++++++
 1 file changed, 35 insertions(+)
 create mode 100644 hackers-git.yml

(limited to 'hackers-git.yml')

diff --git a/hackers-git.yml b/hackers-git.yml
new file mode 100644
index 0000000..f0eef37
--- /dev/null
+++ b/hackers-git.yml
@@ -0,0 +1,35 @@
+---
+# Where to look for "${uid}.yml" files
+#yamldir: "/var/lib/hackers-git/users"
+yamldir: "users"
+
+# The message, if any, that is presented to the user when password
+# modification through PAM is prohibited.
+pam_password_prohibit_message: ''
+
+# Which groups imply membership in other groups (since UNIX groups
+# can't be nested).  Only one level of nesting is supported ATM.
+#
+# That is, if you are in the 'hackers' group, you are also in the
+# 'repo' and 'git' groups, even if they aren't listed.
+groupgroups:
+  hackers:
+  - repo
+  - git
+  - ssh
+  - email
+  - keyring-trusted
+  fellows:
+  - email
+  trustedusers:
+  - keyring-secondary
+  bots:
+  - keyring-trusted
+
+# Groups that are system users that can be ssh'ed into.
+#
+# So, if 'lukeshu' is in the 'repo' group, he can ssh to
+# 'repo'@hostname.
+ssh_pseudo_users:
+- repo
+- git
-- 
cgit v1.2.3-54-g00ecf