deac/gitolite
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity

gl-setup-authkeys had an obsolete usage message

Browse source
This commit is contained in:
Sitaram Chamarty 2011-08-26 07:10:20 +05:30
parent d76c83f948
commit 52cb3e1b8d
1 changed files with 6 additions and 18 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

24
src/gl-setup-authkeys
View file

@ -43,28 +43,16 @@ GetOptions('batch' => \$batch);
unless ($batch) { unless ($batch) {
print STDERR " print STDERR "
This is a cronnable, batchable, program to rewrite ~/.ssh/authorized_keys This is a cronnable, batchable, program to rewrite ~/.ssh/authorized_keys
using public keys in a given directory. It MUST be run by supplying its using public keys in a given directory. You MUST make sure you run the
full path, and the rest of the gitolite scripts must be in the same one that is in the same directory as that used by gl-auth-command (and for
directory. Here's how to run it: what that is, see ~/.ssh/authorized_keys).
/full/path/to/gl-setup-authkeys -batch keydir Except for the deprecated 'from-client' install mode, this should work:
where 'keydir' contains a bunch of '*.pub' files. gl-setup-authkeys -batch keydir
If you're not sure what the full path to the script should be, look in where 'keydir' contains a bunch of '*.pub' files.\n\n";
~/.ssh/authorized_keys for the path to the gl-auth-command script.
If you managed to lose that file (how careless of you!) then, depending on
what install mode you used, it's either \$HOME/.gitolite/src or \$HOME/bin
or /usr/local/bin or whatever your package maintainer decided. I leave it
to you to figure out which method gets you which PATH ;-) In this case
you'll also have to set GL_BINDIR to that same path *and* export it, so
something like this should do:
export GL_BINDIR=/that/full/path/you/just/found
\$GL_BINDIR/gl-setup-authkeys -batch keydir
The keydir can be found from the value of \$GL_KEYDIR in ~/.gitolite.rc\n\n";
exit 1; exit 1;
} }