cd \/root\r\nmkdir -p local\/triggers \r\n<\/pre>\nThen create a script file with the following content:<\/p>\n
#!\/bin\/ash\r\nln -sf ~\/.ssh\/authorized_keys \/etc\/dropbear<\/pre>\nMake the file executable:<\/p>\n
chmod +x local\/triggers\/link-akf<\/pre>\nEdit .gitolite.rc<\/code> as follows:<\/p>\n\n- Uncomment the line
\nLOCAL_CODE \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0=> \u00a0\"$ENV{HOME}\/local\",<\/code><\/li>\n- Immediately below that line add a line with the following content:
\nNON_CORE => 'ssh-authkeys POST_COMPILE link-akf',<\/code><\/li>\n<\/ul>\nTesting and configuring<\/h1>\nCheck the authorized_keys file<\/h2>\n
If everything worked correctly, your \/etc\/dropbear\/authorized_keys<\/code> file should contain your standard ssh keys and<\/strong> a section which looks as follows:<\/p>\n# gitolite start\r\ncommand=\"\/root\/gitolite\/src\/gitolite-shell gitadmin\",no-port-forwarding,no-X11-forwarding,no-agent-forwarding,no-pty ssh-rsa AAAAB3Nza ... and the remainder of the public key\r\n# gitolite end\r\n<\/pre>\nCheck if you can clone a repo from the server to the client machine<\/h2>\n
During the setup, gitolite has created two repositories: gitolite-admin<\/code> and testing<\/code>. The testing<\/code> repo is read\/write for any registered gitolite user while the gitolite-admin<\/code> repo can only be accessed by the gitadmin<\/code> user we specified during the setup. You should now be able to clone the gitolite-admin repo from your client machine:<\/p>\nilek@i7:\/media\/ramdisk$ git clone root@git:gitolite-admin\r\nCloning into 'gitolite-admin'...\r\nremote: Counting objects: 21, done.\r\nremote: Compressing objects: 100% (19\/19), done.\r\nReceiving objects: 100% (21\/21), 3.12 KiB | 0 bytes\/s, done.21\/21) \r\nResolving deltas: 100% (3\/3), done.\r\n0 (delta 0)\r\nChecking connectivity... done.\r\n<\/pre>\nAdding a user and setting permissions<\/h2>\n
If you want to add another user, you just take the new user’s public ssh key, rename it to <username>.pub<\/code> and copy it to the gitolite-admin\/keydir<\/code>. Then run the following conventional git commands:<\/p>\ngit add <username>.pub\r\ngit commit -m \"User <username> added\"\r\ngit push origin master<\/pre>\nIn order to conduct the next test, you should add another user from another machine who will not be admin (neither for oWRT, nor by gitolite; we just want a plain and simple git user who has access to the testing repo). Access rights to the repositories can be granted or withdrawn by editing the gitolite-admin\/conf\/gitolite.conf<\/code> file (which is pretty self-explanatory).<\/p>\nCheck if git users are really ring-fenced from root access<\/h2>\n
Finally you should check if git users who log in through the root ssh access are not able to get access to the root shell – after all you want to be sure that git users cannot execute root commands on your server. With the gitolite account just created, try the following:<\/p>\n
ssh root@<oWRT-IP>\r\n<\/pre>\nIf everything is fine, you should see a message like this:<\/p>\n
PTY allocation request failed for channel 0\r\nsh: hello, <username>, this is root@ running gitolite3 v3.6.3-11-g247156 on git 2.0.0\r\n\r\nhostname: not found\r\n R W testing\r\nConnection to <oWRT-IP> closed<\/pre>\nIf you see your normal oWRT welcome screen after the login, then something has gone awfully wrong and gitolite users can access the root functionalities of your OpenWRT operating system. In that case you should delete the complete gitolite installation from your server and restore the authorized_keys<\/code> file from the backup file you made.<\/p>\ncd \/root\r\nrm -rf .gitolite gitolite\r\nrm .gitconfig\r\ncd \/etc\/dropbear\r\ncp authorized_keys_backup authorized_keys<\/pre>\nUsing git(olite) with Eclipse<\/h1>\n
Once you have a repo on gitolite, it is convenient to directly connect it to a programming IDE like Eclipse. On your local machine, proceed as follows:<\/p>\n
Setting up Eclipse for gitolite<\/h2>\n
Click Window<\/code> \/ Preferences<\/code> and navigate to Network Connections<\/code> \/ SSH2<\/code>:![\"eclipse_network_conn\"](\"http:\/\/hobbykeller.spdns.de\/wp-content\/uploads\/2015\/10\/eclipse_network_conn.png\")
<\/p>\nEnter the ssh home directory (which is usually under ~\/.ssh for Linux machines) and the private<\/strong> key name. If you are on a machine with both root and git access make sure, that it is the git key and not the default key.<\/p>\nThen click the Key Management<\/code> tab, press the Load Existing Key<\/code> and navigate to the public<\/strong> key which corresponds to the private key you specified in the previous tab.<\/p>\nImporting a repository from gitolite into Eclipse<\/h2>\n
Once you have estabished the connection, you can easily import a project from your gitolite server.\u00a0 We are going to import the (empty) testing repository as a Java project and add one file.<\/p>\n
\n- Choose
File<\/code> \/ Import<\/code> from Eclipse’s menu,<\/li>\n- choose
Git<\/code> \/ Projects<\/code> from Git in the following dialog and click Next<\/code>,<\/li>\n- choose
Clone URI<\/code> and click Next<\/code> again.<\/li>\n<\/ul>\nIn the dialog that opens now,<\/p>\n
\n- fill in the Host<\/strong> field with the IP Address of your Git Server (or the FQDN),<\/li>\n
- the Repository Path<\/strong> with the name of the repository you want to clone (
testing<\/code> in our case),<\/li>\n- Set the Protocol<\/strong> to ssh,<\/li>\n
- and enter the User<\/strong> name – which in case of our OpenWRT installation should be
root<\/code> (remeber that gitolite always clears through a central user and uses the ssh key to map the central user to the actual gitolite user)<\/li>\n- the URI<\/strong> field is filled automatically, the Port<\/strong> and Password<\/strong> fields remain empty<\/li>\n<\/ul>\n
![\"eclipse_git_location\"](\"http:\/\/hobbykeller.spdns.de\/wp-content\/uploads\/2015\/10\/eclipse_git_location.png\")
<\/p>\n
After clicking Finish<\/code> you will come to a dialog in which Eclipse warns you that you import an empty repository – nothing to worry about as gitolite has set up the testing repository without any content.<\/p>\nThe New Project Wizard will then take over. Choose Java for this example, give a meaningful project name and hit Finish<\/code> again.<\/p>\nOnce you have finished that procedure, Eclipse will have cloned a local copy of your git repository to your client. You can work on that copy as before.<\/p>\n
<\/p>\n","protected":false},"excerpt":{"rendered":"
If you want do serious programming, you sooner or later need to work with a version control system such as Subversion, Mercrurial or – probably the best choice – git.Continue readingRunning a git server on OpenWRT<\/span><\/a><\/span><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[64,16],"tags":[137,135,136,17],"class_list":["post-718","post","type-post","status-publish","format-standard","hentry","category-linux","category-openwrt","tag-eclipse","tag-git","tag-gitolite","tag-openwrt"],"_links":{"self":[{"href":"https:\/\/hobbykeller.spdns.de\/index.php?rest_route=\/wp\/v2\/posts\/718","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/hobbykeller.spdns.de\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/hobbykeller.spdns.de\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/hobbykeller.spdns.de\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/hobbykeller.spdns.de\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=718"}],"version-history":[{"count":10,"href":"https:\/\/hobbykeller.spdns.de\/index.php?rest_route=\/wp\/v2\/posts\/718\/revisions"}],"predecessor-version":[{"id":960,"href":"https:\/\/hobbykeller.spdns.de\/index.php?rest_route=\/wp\/v2\/posts\/718\/revisions\/960"}],"wp:attachment":[{"href":"https:\/\/hobbykeller.spdns.de\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=718"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/hobbykeller.spdns.de\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=718"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/hobbykeller.spdns.de\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=718"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}