Hello,
Thank you for your very useful replies (and apologies for the delay in
mine, I had a
bit of trouble understanding how exactly GNUnet VPN is used).
To give a bit of an update, I got it running via GNUnet VPN. It is, in
my experience,
sometimes slower, but more reliable (no more delays need to be added at
random,
server-side or client-side).
I have also figured out a way to authentify users via gnunet-identity,
to allow for pushing
repos (as long as the user is allowed to by the server). It uses the
encryption facilities of
gnunet-identity to get the client to return a one-time
randomly-generated password sent
to it encrypted by the server (well, the client actually sends back a
sha256 hash of it, to
avoid a malicious server asking the client to decrypt real messages
addressed to it).
So, it is now technically possible to manage one's git repos entirely
via GNUnet (though
it can be impractical, because connection can sometimes take a while).
Thanks again,
Have a nice day,
Amélia Coutard-Sander.
P.S.: Thank you for pointing out the issue with https cloning, it should
now be working correctly.
The repo is still available at
https://git.ameliathe1st.gay/?p=git-over-gnunet.git, and the corresponding
git-over-gnunet URI is specified on the gitweb page, though
git-over-gnunet is not retrocompatible with
the state the implementation was in when I sent it the first time (so it
is impossible to get this new
version using the old version of git-over-gnunet).
