I recently emerged the gitosis package, however I was unable to connect to the server until I added the newly created git user to the ssh group. Otherwise sshd blocked all connections. I believe this is the default behavior of sshd. The current gitosis tutorial [http://en.gentoo-wiki.com/wiki/Gitosis] recommends that the user modifies /etc/shadow to allow ssh access. I believe adding the user to the ssh group is a more appropriate solution, assuming that the user has not disabled or otherwise modified the allowed groups for sshd. However if that is the case the user is likely aware of this. I made a trivial modification to the ebuild to also add the git user to the ssh group. I tested it on my machine and this allowed me to immediately clone the gitosis-admin repository after running the gitosis-init command. I did not need to muck about in /etc/shadow. I'd like to open a discussion about adding this feature to the ebuild. Are there any unintended consequences I am missing? Reproducible: Always Steps to Reproduce: $ sudo emerge gitosis $ sudo -H -u git gitosis-init < id_rsa.pub $ git clone git@<server>:gitosis-admin.git Actual Results: A password prompt is presented. sshd will reject any connetions. Expected Results: The repository is cloned into ./gitosis-admin/ using the user's rsa key
Created attachment 298421 [details] Trivial update to ebuild to also add user to ssh group
gitosis is being lastrited.
