Veja Gitolite e ssh
Restricting users to specific commands is very important for gitolite.
If you readman sshd
and look for authorized_keys file format, you'll see a lot of options you can add to the public key line, which restrict the incoming user in various ways. In particular, note thecommand=
option, which means "regardless of what the incoming user is asking to do, forcibly run this command instead".Also note that when there are many public keys (i.e., lines) in the authorized_keys file, each line can have a different set of options and
command=
values.Without this
command=
option, the ssh daemon will simply give you a shell, which is not what we want for our gitolite keys (although we may well have other keys which we use to get a shell).This is the backbone of what makes gitolite work; please make sure you understand this.
Aqueles command=
estão usando o nome da sua chave pública como nome de usuário.
Assim, todas as suas consultas ssh são feitas com:
- o usuário git
- uma chave pública cujo nome está registrado nos parâmetros da diretiva command = no
~git/.ssh/authorized_keys
.
Quanto a user/repos
, o mais próximo que você teria do Gitolite é em repositório selvagem e padrão de recompra .
repo CREATOR/a[0-9][0-9]