Tag Info

Hot answers tagged

20

This is expected behaviour according to the manpage of ssh_config: IdentityFile Specifies a file from which the user's DSA, ECDSA or DSA authentica‐ tion identity is read. The default is ~/.ssh/identity for protocol version 1, and ~/.ssh/id_dsa, ~/.ssh/id_ecdsa and ~/.ssh/id_rsa for protocol version 2. Additionally, ...


9

I haven't tested this, but I believe that after you run your dpkg-reconfigure on an example machine, you can run debconf-get-selections | egrep "^gitolite\s" to get what was set. (it's in the debconf-utils package if you don't have it). Then on the CLI, debconf-set-selections $FILENAME before running apt. Then with puppet it would be something like: file ...


7

You can actually see the efficiency on GitHub as to how fast this is. You are not going to cause a significant bottleneck with that many keys. Though as documented in their blog from 2009, they have changed how ssh keys are retrieved, from a database. Hat Tip: @Jeremey But, you created over 8k keys, you can test again with 50k keys. Those keys don't need ...


6

I am constantly doing this by hourly crontab job for faster local deployment. (which creates an exact copy of the original server, serves as a read-only mirror, personally I call it a puppet machine). All you need to do is: backup/restore mysql data (tools: mysqldump / mysql < backup.sql.txt) copy all gitlab www to new machine (scp, rsync) copy all ...


6

Being able to access gitolite@server:~/repositories/gitolite-admin.git, but not gitolite@server:gitolite-admin indicates you are not going “through” Gitolite, but just using plain SSH-based access to the gitolite user. If ssh gitolite@server echo normal access yields normal access, then the key you are using is not restricted to going through Gitolite. If ...


4

Gitolite 2.x If git is not in the default PATH, then you can set $GIT_PATH in your gitolite user’s ~/.gitolite.rc. The default .gitolite.rc comes with this line: $GIT_PATH=""; If your Git installation is under /usr/local (so that you have /usr/local/bin/git), then replace the above line with this one: $GIT_PATH="/usr/local/bin"; See “support for git ...


4

You need to provide a preseed to work around this. See how it is done for Java in this module. I find that the easiest way to get a preseed file is to do a manual installation and configuration first, and then getting the seed from that. This blog has a good example of this.


4

he asks not only for the passphrase of my rsa_key but also for the password of the gituser. That means the ssh has failed to authenticate the request through the public_key (either because said public key hasn't been found on the client side, or is incorrectly registered on the server side, or the passphrase hasn't been provided, is the key is ...


3

To add an 'aliased' user git for gitolite, you can do something similar to the following [ec2-user@ip-10-170-94-162 ~]$ sudo useradd -m foo [ec2-user@ip-10-170-94-162 ~]$ getent passwd foo foo:x:500:502::/home/foo:/bin/bash [ec2-user@ip-10-170-94-162 ~]$ sudo useradd -o -d/home/foo -u500 -g502 -s/bin/bash -M foo2 [ec2-user@ip-10-170-94-162 ~]$ getent ...


3

git push --force is really the only one that you need to worry about. The other one that could cause issues would be removing a branch, but at least with gitolite if you can't push --force then you can't delete a branch.


3

This address won't ever work: git clone username@IPAddress:newRepoName.git When using gitolite, you always use the same account: git clone git@IPAddress:newRepoName.git (if git is the account under which gitolite is installed) See "adding and removing users" to understand how to declare a new user: Ie adding his/her public key named after the user id ...


3

You can disable password logins for that specific user. You can't provide a specific message, but at least they won't be prompted for a password. Add the following in /etc/ssh/sshd_config: Match user git PasswordAuthentication no ChallengeResponseAuthentication no


3

First of all: congratulations for not disabling SELinux and trying instead to understand it and configure it properly. Filtering the AVC denials you posted in your question makes much more clear what the problem could be: # cat avc_denials | audit2allow #============= httpd_sys_script_t ============== allow httpd_sys_script_t gitosis_var_lib_t:dir { read ...


3

This should be possible if you set up your linux server to user kerberos authentication to authenticate clients against the same active directory infrastructure as the windows clients. Haven't tried it though, and never heard of anyone doing it. But git doesn't impose any restrictions on how the SSH connection should work, so as long as the windows SSH ...


2

You can use hooks to accomplish this. It has been discussed on stackoverflow. http://stackoverflow.com/questions/7147699/limiting-file-size-in-git-repository


2

Why not use a post-receive hook to send commit messages to a mailing list (per-project, managed by majordomo or similiar) and let people subscribe/unsubscribe to the list? Then all you have to do is create the per-project mailing lists once and let the software deal with the rest.


2

I am assuming everyone is sharing the same user on the git server, and they each have their own key to log in with. If that is the case, then instead of identifying the remote user, you could easily identify the public key that the user used to log into the git server. To do that, you should allow PermitUserEnvironment in your server's sshd_config, and then ...


2

You need to generate/add the key for each user/client machine combination that will be using gitolite. The keys get copied into your gitolite-admin/keydir directory (I use a $USERNAME-$HOSTNAME-id_rsa.pub naming convention-- not sure if that's required but it works for me). Once youve added the keys to the keydir directory then you need to update the ...


2

As mentioned in the sources of gitolite install: Simplest use, if $HOME/bin exists and is in $PATH, is: git clone git://github.com/sitaramc/gitolite gitolite/install -ln So make sure your $HOME/bin exists and is in $PATH.


2

You need to add a gitweb.conf.pl file (like this one) which: will be called by gitweb (if that file exists and defines a export_auth_hook sub, gitweb.cgi calls it) will specify where the git repos are will call gitolite That would include: $ENV{GL_REPO_BASE_ABS} = "$ENV{HOME}/repositories"; $export_auth_hook = sub { my $repo = shift; my $user = ...


1

Check here. Below the file list, there's an online readme with a general configuration strategy and a long step-by-step configuration section that might be helpful.


1

It seems there are currently a lot of people working on "2.0-migration" branches of the redmine_git_hosting plugin originally made by Eric Paul Bishop on GitHub. Currently the most advanced of the forks containing these branches is the one by a guy called zucchi. After looking around for some time, I guess there is no production-ready variant of the plugin ...


1

I did this plugin, check it out! https://github.com/jbox-web/redmine-gitolite This works with Redmine 2.x only I've finally updated Redmine Git Hosting from Kubitron's You can check out it here https://github.com/jbox-web/redmine_git_hosting This one is compatible with Redmine 1.x and 2.x. The differences are : a cleaner indentation, the code is a ...


1

i think you have to change your sshd_config file: PasswordAuthentication no or add Match User yourUser PasswordAuthentication no


1

Maybe you did not run the rake command as your gitlab user? As in: sudo -u gitlab bundle exec rake gitlab:app:status RAILS_ENV=production Had a similar problem, seeing other settings from gitlab.yml just not being applied...


1

I believe NSS-LDAP will provide system level access control via LDAP. (http://www.padl.com/OSS/nss_ldap.html) As long as gitolite uses the system level NSS to determine the access control, that should be your best bet. So the answer to both questions is "Yes, it can be done", but you will need to setup the system to accommodate (and I am fully blindly ...


1

I had the same problem, I solved it by adding AllowUsers git in /etc/ssh/sshd_config file


1

You don't need to use ssh for his. If you add the www-data user to the gitolite group your webserver should be able to read the repositories from the filesystem.


1

I found the solution following http://stackoverflow.com/questions/3817478/setting-up-git-server-on-windows-with-git-http-backend-exe and http://stackoverflow.com/questions/8021167/git-debian-apache-and-smart-http which was to add the SetEnv REMOTE_USER=$REDIRECT_REMOTE_USER to my apache configuration and use $REMOTE_USER in my script which contains indeed ...


1

Moving gitolite seems easy: you need to make sure the public keys it references are still in the ~/.ssh/authorized_keys of the new home (so you mainly need to copy that file over) And you need to move the repositories, .gitolite and .gitolite.rc files (check the paths in that last one) The "users" are only declared in the gitolite file and the gitlab ...



Only top voted, non community-wiki answers of a minimum length are eligible