aboutsummaryrefslogtreecommitdiff
blob: 50d9c4b1aed316a253dfc212ec38456e66fc66f4 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
gitolite-gentoo:

Features:
	SSH-Keys behavior
		Also allow comments
		Add the ability to preserve key options like from="1.1.1.1" (AUTH_OPTIONS_PRESERVE)
		Some kind of key validation

	Additional metadata can be provided to be passed to the gitolite environment
		This can be useful if you want to pass additional metadata to the hooks,
		for e.g. cia.vc or other services.
		You can set a list of allow/parsed variables (GL_METADATA) and a list of
		*required* variables (GL_METADATA_REQUIRED).

		Example:
		.gitolite.rc:
		%RC = (
		...
			GL_METADATA => [ 'realname-ascii', 'cia-user' ],
			GL_METADATA_REQUIRED => [ 'realname-ascii', 'cia-user' ],
		...
		)

		keydir/$user.pub:
		# realname-ascii: foo bar
		# cia-user: foo
		ssh-rsa ... user@host

		The hooks can then use $realname_ascii and $cia_user from the
		environment.
		Each '-' (dash) will be replaced by an '_' (underscore).

		If you want other metadata or information from the .pub files, you
		should look at the base Gitolite v3 documentation for "distinguishing
		one key from another" and enable the '--key-file-name' option to
		'ssh-authkeys'.

Non-Features:
	SSH-Keys
		In Gitolite-Gentoo v2 we supported multiple keys in a single file. This
		support is discontinued. You should migrate to one key per user; we are
		using $EMAIL@$N for Gentoo in future.