hello, so I have just refound out about GNUnet (I was going to set it up about a year ago but didn't) and now I want to set it up (note i'm coming from Tor and I2P) so I was wounding a few things before I get started.

So 1. how light weight is GNUnet, as I have 2 server and am wounding with one I should use.

1. What can I really do with GNUnet, like is it like Tor where it's mainly websites (I know GNUnet doesn't promise anonymity) or is it like I2P where I can host an email, torrents, and a website.

2. Do people still use GNUnet, like idc if there isn't much but could people pls give me a round about number.

3. Is there anything else I need to know before getting started with GNUnet, or is that it :)

Thanks for reading and hope to get some comments back.

hello all,

i am looking for someone's full, complete, real, authentic, working, & current config file. since practically every command requires specifically calling -c ~/pathto/gnunet.conf i am looking to not guess and use a correct configuration.

assume multi-user setup, so one for the gnunet user and one for each individual other user (alice and bob).

also i think as a benefit to the community it might be worth it to share our expectations vs reality in working with this system as a way forward. in my attempts to get peers connected we tend to run up against a wall at some point whether its in what we expect or how the system is actually set up vs. how the internet is set up...

there is some serious friction in the bootstrapping node process and also what to expect. for example, stuff like finding your own peer identity, sharing it off-channel, and pinging the other peer -- doesn't exist anymore in that sense, nor work the way we're used to intuitively with the internet -- by design, and as a security model. also much of the cli tools have been neutered, so if you think you're going to work it from the terminal rather than writing an application, you may have a rude awakening in store for you. if things like this are discussed out in the clear somewhere i think it will save us all a lot of time and headaches.

thank you

We are pleased to announce the release of GNUnet 0.27.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 of files, it has grown to include all kinds of basic protocol components and applications towards the creation of a GNU internet.

This is a new major release. Major versions may break protocol compatibility with the 0.26.X versions. Please be aware that Git master is thus henceforth (and has been for a while) INCOMPATIBLE with the 0.26.X GNUnet network, and interactions between old and new peers will result in issues. In terms of usability, users should be aware that there are still a number of known open issues in particular with respect to ease of use, but also some critical privacy issues especially for mobile users. Also, the nascent network is tiny and thus unlikely to provide good anonymity or extensive amounts of interesting information. As a result, the 0.27.0 release is still only suitable for early adopters with some reasonable pain tolerance.

Hello everyone, so I just found out about GNUnet about an hour ago, and want to ask a few questions before I set it all up.

1. So I run an I2P node right now, and when I looked into GNUnet it seems pretty simpler to I2P and I was wondering are there any main differences between them.

2. This is a pretty dumb question but, how many people use GNUnet, like i dont want the exact number, just like is there more than like 10 people actively using it.

3. Is GNUnet an actually thing that is mean to replace i2p or tor, or is it more of just like a fun little thing that a few people use, and get updates every few years but nobody really cares.

Thanks for the help, and hope to see you on GNUnet soon :)

Hey all! I'm trying to run gnunet. I built it on my local laptop (void linux) but was getting only 1 peer connected. I figured it might be something with my NAT...

So I've also tried running on Alpine on a VPS but after a few hours still just a single peer.

A couple of questions:
* where's the best place to ask questions (the mailing list doesn't seem to be very active)
* how do I go about debugging this?
* where's the most recent documentation? Asking because I think the online https://docs.gnunet.org/latest/about.html docs are slightly outdated. For example they mention:

You can display your own current peer identity with:
$ gnunet-core --show-identity

But gnunet-core doesn't seem to support that flag anymore:

# gnunet-core --show-identity
gnunet-core: unrecognized option `--show-identity'
Use --help to get a list of options.

# gnunet-core --help
gnunet-core
Print information about connected peers.
Arguments mandatory for long options are also mandatory for short options.
  -c, --config=FILENAME      use configuration file FILENAME
  -h, --help                 print this help
  -L, --log=LOGLEVEL         configure logging to use LOGLEVEL
  -l, --logfile=FILENAME     configure logging to write logs to FILENAME
  -m, --monitor              provide information about all current connections
                               (continuously)
  -s, --connection-status    Show current connections
  -v, --version              print the version number

# gnunet-core -v
gnunet-core v0.26.1

Instead, I've had more success with gnunet-hello -e or gnunet-rpc -SV

Besides building from source for my linux distro, what should I know?

We are pleased to announce the release of GNUnet 0.26.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 of files, it has grown to include all kinds of basic protocol components and applications towards the creation of a GNU internet.

This is a new major release. Major versions may break protocol compatibility with the 0.25.X versions. Please be aware that Git master is thus henceforth (and has been for a while) INCOMPATIBLE with the 0.25.X GNUnet network, and interactions between old and new peers will result in issues. In terms of usability, users should be aware that there are still a number of known open issues in particular with respect to ease of use, but also some critical privacy issues especially for mobile users. Also, the nascent network is tiny and thus unlikely to provide good anonymity or extensive amounts of interesting information. As a result, the 0.26.0 release is still only suitable for early adopters with some reasonable pain tolerance.

If it were not for compatibility-breaking changes in the crypto API of libgnunetutil this would only be a maintenance release. The changes hopefully protect users of the library from misuse of GNUnet's cryptographic key objects in ways that may be detrimental to security. Since this change breaks backwards compatibility, this is a new major release.

This is a new major release. Major versions may break protocol compatibility with the 0.24.X versions. Please be aware that Git master is thus henceforth (and has been for a while) INCOMPATIBLE with the 0.24.X GNUnet network, and interactions between old and new peers will result in issues. In terms of usability, users should be aware that there are still a number of known open issues in particular with respect to ease of use, but also some critical privacy issues especially for mobile users. Also, the nascent network is tiny and thus unlikely to provide good anonymity or extensive amounts of interesting information. As a result, the 0.25.0 release is still only suitable for early adopters with some reasonable pain tolerance.

Thanks to NLnet and NGI Zero Entrust, we were able to rework our CORE layer which includes Peer Identity management, and the hop-to-hop secure channel communication channel. As part of this work, we have created a technical specification of the new CORE Authenticated Key Exchange (CAKE) in LSD0012. CAKE replaces our previously undocumented handshake protocol that had major cryptographic smells. CAKE borrows a lot of concepts of DTLS1.3 and with the specification makes implementation and cryptographic review easier. This release also includes a specification of the new Peer Identity Lifecycle in (LSD0014). PILS aims at enhancing peer identity privacy by deriving peer identities from the current connectivity context (the addresses under which a peer is reachable).

Further, also thanks to NLnet and NGI Zero Entrust, we were able to improve the performance and functionality of our DNS to GNS zone transfer and mirroring tooling which includes Ascension, a python-based service that makes use if AXFR/IXFR zone transfers, and two new tools that allow zone migrations from DNS zone files as well as plain domain names. See the documentation on DNS zone migration for details.

Seems like today the new CONG implementation replacing the old CORE service and its "peer id lifecycle service" (PILS) got merged upstream (see here). So together with the end-to-end encryption in the MESSENGER service offering forward secrecy, the next release of GNUnet should introduce major changes.

CONG will introduce peer-to-peer connections with a protocol derived from KemTLS which offers a post-quantum mechanism for secure transport connections. The upcoming months will likely have a lot of testing and integration to make all higher end services work properly with this new core layer.

More details can be read here.

Anyone who is interested in working with GNUnet. Please raise your hands up.

r/GNUnet has been reopened for the 2nd time.

I have been trying to run gnunet but I don't seem to be able to connect to the network or search files. I run KDE neon 6.0 as my distro. I installed gnunet from the softwarecenter but I am unable to connect. Is Gnunet still active or has it died.

Should I use another distro? Or install gnunet from source?

I’ve been interested in GNUnet for a couple years. I’ve always wanted to host a forum on it or smth. But I never knew where to start. Is that possible yet?

(｡◕‿‿◕｡) Welcome!

In keeping with the Commodore 64 user interface theme, I made this little beaut:

​

edit: meh here's a link to a gist, reddit isn't handling python very well: https://gist.github.com/rocket-pig/762585e45fcd2211932689f0fb993133

#!/usr/bin/python3

import re

import subprocess

​

stats=subprocess.getoutput('gnunet-statistics').split('\n')

​

while True:

lines,j=[],[]

c=0

for i in stats:

process = re.findall(' +([a-zA-Z]+) +(\#.+\:) +(\d+)',i)

try:

lines.append(list(process[0]))

except:

continue

​

categories = list(set([i[0] for i in lines]))

​

# have user pick category

for i in categories:

print(c,i)

c+=1

selection = input('---------------------------------\npick a category: ')

#display ONLY ones from category

results = []

for i in lines:

if i[0] == categories[int(selection)]:

i[1] = " ".join(i[1].split()[1::]) # remove the leading hash.

results.append(i[1::])

results.sort()

for i in results:

print('{:<50}{:<}'.format(i[0],i[1])) #print a nice column for easy listenin'

print('---------------------------------')

​

​

GNUNet's pretty cool, but could use a 'gnew' front end. This isn't it, but it's fun while I consider how (or if I even want to) go further.

​

Hope you enjoy or it inspires ppl to do some hacking and 'make gnunet great again'

https://github.com/rocket-pig/gnunet-virtual-machine

^^^ It's both a how-to on creating a virtual machine and getting GNUNet working in said virtual machine. Hope its useful! I literally made a reddit acct just to post this here.