Re: Git over GNUnet

--=-tsr6xG4ZRr4GfnZaKyvm
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Correction: The GNS resolver no longer synthesizes VPN records to IP
addresses.
You need to resolve the IP (A record) through the dns2gns DNS server or
use gnunet-vpn and the information from the VPN record to do that.

BR


On Thu, 2024-11-28 at 12:39 +0100, Martin Schanzenbach wrote:
> Actually, there is a way you can simplify this feature:
>=20
> There is record type called "VPN".
>=20
> Its string format is: "<proto> <peerIDstring> <service>"
>=20
> The protocol is whatever protocol you want to use (e.g. git, http
> etc).
> The service string is some service descriptor you can also choose.
>=20
> Then you can setup a VPN service locally:=C2=A0
> see
> https://www.gnunet.org/en/use.html#vpn
> and
> https://docs.gnunet.org/latest/users/vpn.html
>=20
>=20
> GNS can automatically synthesize an IP address and communication will
> be established via cadet automatically.
>=20
> BR
> Martin
>=20
>=20
> On Thu, 2024-11-28 at 11:43 +0100, Martin Schanzenbach via
> Mailinglist
> for GNUnet developers wrote:
> > Hello,
> >=20
> > thanks for tinkering with the GNS+Cadet stacks :)
> >=20
> > Here is what I got from my peer:
> >=20
> > "
> > GIT_EXEC_PATH=3D$GIT_EXEC_PATH:$HOME/dev/git-remote-gnunet git clone
> > gnunet://git.serv.amelia.gnunet.gns.alt/git-over-gnunet
> > Cloning into 'git-over-gnunet'...
> > Looking up git.serv.amelia.gnunet.gns.alt.
> > Attempting to connect to peer
> > DESNPFW7GF0NT3XZ9GJ5JPK18JF6DFZ9PD01QS31X8T93AN8X12G, on port
> > `git.git-
> > over-gnunet.git-upload-pack'.
> > remote: Enumerating objects: 44, done.
> > remote: Counting objects: 100% (44/44), done.
> > remote: Compressing objects: 100% (40/40), done.
> > remote: Total 44 (delta 18), reused 0 (delta 0), pack-reused 0
> > (from
> > 0)
> > Receiving objects: 100% (44/44), 15.22 KiB | 7.61 MiB/s, done.
> > Resolving deltas: 100% (18/18), done.
> > "
> >=20
> > As you can see, "git.serv.amelia.gnunet.gns.alt" which you
> > registered
> > via fcfs.gnunet.org also works.
> > I am generally surprised that cadet works. Not so much that GNS
> > works
> > ;)
> >=20
> > Regarding your TODO and writing it as a "proper GNUnet service": I
> > do
> > not think that is actually necessary. Using CLI tools and chaining
> > them
> > like it is done right now is the UNIX-way of doing things, and
> > there
> > is
> > nothing wrong with that.
> >=20
> > Good job
> > Martin
> >=20
> > P.S: unlike using the remote-gnunet, I am unable to clone your repo
> > using "traditional" means. The HTTPS URL cannot be cloned, the SSH
> > link
> > I cannot use for obvious reasons.
> >=20
> > On Wed, 2024-11-27 at 16:40 +0100, Am=C3=A9lia Coutard-Sander wrote:
> > > Hello,
> > >=20
> > > In case anyone is interested, over the last few days, I have
> > > coded-
> > > up
> > > a=20
> > > prototype
> > > (in bash) for a way to clone (and fetch, and pull) git repos over
> > > GNUnet.
> > > The git repo with the code is over at=20
> > > https://git.ameliathe1st.gay/?p=3Dgit-over-gnunet.git,
> > > if you want to check it out.
> > >=20
> > > Once you've obtained the source once, you can clone the repo
> > > *using*
> > > git=20
> > > over
> > > gnunet, at the address=20
> > > gnunet://git.serv.000G0000V4BD1K10PRPGDKR916362AFZ12DBGA378EFRWPB
> > > 0M
> > > 54
> > > WHGX3YC/git-over-gnunet=20
> > > .
> > > See the README.txt for more details.
> > >=20
> > > It doesn't always work (and I haven't gotten pushing to work),
> > > but
> > > I=20
> > > think that it
> > > might be an issue with the gnunet-cadet cli (because it, for
> > > example,
> > > doesn't open
> > > the connection if stdin reaches eof before the connection
> > > attempt).
> > > I'll try to investigate further.
> > >=20
> > > Thanks in advance for you interest and/or (more importantly)
> > > criticism,
> > > Have a nice day,
> > > Am=C3=A9lia Coutard-Sander.
> > >=20
> > >=20
> >=20
> >=20
>=20


--=-tsr6xG4ZRr4GfnZaKyvm
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----

iQJIBAABCAAyFiEEPREGPBD5jRS9JNFHCwmY74b1m2oFAmdIWhUUHHNjaGFuemVu
QGdudW5ldC5vcmcACgkQCwmY74b1m2pp1xAAu2ma91xykRHcMCLy26XJUNhUyPEs
JBVSbRW/6Oq5sSsvZ/k0RoDaqvA3tLQAUfB4iLTWUchg1VJBHfovslh3u/EU9vSz
ez48RDUFWHrk6/JWeAoXsH8GUJNsOm4LcSZ05wiJ4nsY9rl48yYsC7zn7u/H5LNK
lOv8q44cUX1TUOfzypNcLSIYAsIzkT2cp855YMNG+soJRrCnZLI0MVU5BLWwLHc7
QbArQqMQyf+IZKO++nv0FnHZTZSoUm5j6zfCQ+6t3PT94so9OZL0QP301OnXlE8v
1SOI7n8/EjuY2mJ5rgHFiSQYP8HFsBX6xZyGIbRKysoVGAyDnDzQVfHzg/0Zx0lF
wnOCsjmIG2/o7BvNKHMml66X+fdJEf7AMteoghWVWmENXh7wFVr6rk/YGIdVObFm
arnH+n714QKIdXdLdfMbS4jSOqEmZwyaR17GEOt0f3i4CycMRFBZkra96/HagYgM
iidm9YrDBYcUt8H+7WhbYEFpQI3M5riQGim55PNd0uKhE+vJe/747qfsi/6ja6qb
S9sTGyR087Tqyagif9qRNO6lna6CySZ7q+1iOAFmDre7qSpqffll+YOpI968UHiC
8m5FFwLrlK08FHQBpUXmfFNxSR7F8WmkhAQIexwOGFMrWfIGmvMG8UTM1TlScBJL
VRksWGIg7jp2dqw=
=x2G2
-----END PGP SIGNATURE-----

--=-tsr6xG4ZRr4GfnZaKyvm--