OpESec has deployed the first of many GIT services. This is just like GITLab/BitBucket/GitHub without the central control and logging.
This is a Tor v3 hidden service, which means that at least Tor 0.3.2.9 is required to access it.
To clone anew, do:
git -c http.proxy=socks5h://127.0.0.1:9050 clone http://rau4szczlwhqdmkgzb6yzy7cqwnmm472mzusneb7rp5p4npmw7hputid.onion/{user}/{repo}.git
cd {repo}
git config --add remote.origin.proxy "socks5h://127.0.0.1:9050"This assumes Tor proxy is set up on 127.0.0.1:9050 - the default. The last command is necessary to make sure that pulls for updating also go through the proxy. A full clone might be slow, so consider doing a shallow clone (--depth=10 or such) if not all of history is required.
Or if you already have the repo cloned:
cd {repo}
git remote add opesec http://rau4szczlwhqdmkgzb6yzy7cqwnmm472mzusneb7rp5p4npmw7hputid.onion/{user}/{repo}.git
git config --add remote.opesec.proxy "socks5h://127.0.0.1:9050"
# and then to pull changes: git pull opesec masterTo verify authenticity, always make sure that at least the top commit is correctly signed (get the maintainer GPG public keys somewhere else):
git log --show-signature
As with all OpESec projects, understand that these are recommendations to get you running. Please understand proxies and TOR, and generate your own OpESec Plan. A good modification to this is to have a dedicated proxy into TOR from a secure network so you don't need TOR running on all machines doing coding. If you do this, you would change the 127.0.0.1 to your local IP address of the proxy device and use the modified port you share.
As with all things, if you wish to register, an email address is suggested. The service should not care if the email address is valid, however securing email is a separate project to be discovered.