blob: 517c3815ad0b19cb2bebf3c4f687b77e773a059d (
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
43
44
45
46
47
48
49
50
51
52
53
|
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,
e.g. notification services, or extra validation.
You can set:
- list of allow/parsed variables (GL_METADATA)
- list of *required* variables (GL_METADATA_REQUIRED).
- list of *appended* variables (GL_METADATA_APPENDED).
Example:
.gitolite.rc:
%RC = (
...
GL_METADATA => [ 'realname-ascii', 'github-user', 'gpg-fpr' ],
GL_METADATA_REQUIRED => [ 'realname-ascii', 'gpg-fpr' ],
GL_METADATA_APPENDED => [ 'gpg-fpr' ],
...
)
keydir/$user.pub:
# realname-ascii: foo bar
# github-user: foo
# gpg-fpr: 0123456789ABCDEF
# gpg-fpr: ABCDEF0123456789
ssh-rsa ... user@host
The hooks can then use the variables from the environment, and they
should available as follows:
realname_ascii='foo bar'
github_user='foo'
gpg_fpr='0123456789ABCDEF ABCDEF0123456789'
Each '-' (dash) will be replaced by an '_' (underscore).
If you want other metadata or information from the .pub files, you
must 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.
|
GitWeb
