The current recommended way according to the documentation
“The simplest and most understandable is to put their keys in different
subdirectories [inside your /kedir], (alice.pub, home/alice.pub,
laptop/alice.pub, etc).”
reference: https://gitolite.com/gitolite/basic-admin.html#multiple-keys-per-user
The old way
If you are asking how you accomplish the following:
- David (home computer)
- David (work computer)
- David (laptop)
With different ssh keys on each computer you would simply create the key (ie: keygen “david@someemail.com”) and then copy the public key to your gitolite keydir directory (gitolite-admin/keydir). When you do that simply name the key david@homecomputer.pub, david@workcomputer.pub, and david@laptop.pub. Add the keys to the repository (git add keydir/.), commit (git commit -m "added David's additional keys") and git push back to the server.
Gitolite is smart enough to know that even though it is a different key the user name (before the @) is still david and will let that user log in and use the ACL for david
Hope this helps
To fix a scenario where you might have john_home.pub john_work.pub open up your gitolite repo (admin repo) and rename the keys in your kedir to john@work.pub and john@home.pub commit and push. Now your user john can login from either machine and use the same username.
Keep in mind, in order for this to work, the email address in the SSH Keys needs to be the same for all of the user’s keys. So using the example above, in the keys david@homecomputer.pub, david@workcomputer.pub, and david@laptop.pub all should have the email address of david@foobar.com.
Above was the “old way” do to this and may cause a complication if you have named your keys in the “email address way” contrary to what I stated above gitolite DOES NOT inspect your key for the proper email address. Please ignore (I left the original comment in for clarity).