To say it a bit more bluntly: Using the GNUnet configuration as your
own application's configuration was never a good idea.
After all, none of the paths actually belong to your application and
you probably should not mess with any of those.
This is why you should pass your applications own Project
We are pleased to announce the release of GNUnet 0.23.0.
GNUnet is an alternative network stack for building secure,
decentralized and privacy-preserving distributed applications. Our goal
is to replace the old insecure Internet protocol stack. Starting from
an
application for secure publication
det automatically.
>
> BR
> Martin
>
>
> On Thu, 2024-11-28 at 11:43 +0100, Martin Schanzenbach via
> Mailinglist
> for GNUnet developers wrote:
> > Hello,
> >
> > thanks for tinkering with the GNS+Cadet stacks :)
> >
>
setup a VPN service locally:
see
https://www.gnunet.org/en/use.html#vpn
and
https://docs.gnunet.org/latest/users/vpn.html
GNS can automatically synthesize an IP address and communication will
be established via cadet automatically.
BR
Martin
On Thu, 2024-11-28 at 11:43 +0100, Martin Schanzenbach
Hello,
thanks for tinkering with the GNS+Cadet stacks :)
Here is what I got from my peer:
"
GIT_EXEC_PATH=$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.
Atte
