Dealing with the spam

We've recently been targeted more and more by spammers. Making the captcha's harder doesn't seem to stop them (just makes it nearly impossible for normal humans to submit...), and the automated posts are just too much work to deal with on a daily basis. So we're changing the process for postings by adding another access level: "real" users. After you sign up for an account, you will only be an "authenticated" user, which means you can see some data usually hidden, but posting is restricted to comments, and those are also moderated.

Reviving the discussion: gnunet's p2p chat

It is on the todo list for GNUnet, but nothing about it can be found on this website. The discussion was mainly on GNUnet's old website, long gone, but a leg of the discussion (and "possible design" for GNUnet's P2P chat is here:

Unfortunately the old Drupal had a quite more extensive discussion (at least one thread that started here, and went on with possible implementation details), but, well, better small documentation then none :-)

Ein neues gnunet-setup

Es gibt jetzt einen ersten Entwurf eines Einrichtungswerkzeugs für die kommende Veröffentlichung von GNUnet 0.9.0. Anders als das Guile-basierte gnunet-setup von 0.8.x nutzt dieses neue Werkzeug Glade und Gtk+, was es für Designer einfacher macht, das UI zu verbessern - und es hoffentlich einfacher für Entwickler macht, auch Funktionen zur Auto-Konfiguration hinzuzufügen um den "Assistenten"-Modus obsolet werden zu lassen.

Eine Kopie des Quelltextes findet sich unter

A new gnunet-setup

We now have an initial draft for a setup tool for the upcoming GNUnet 0.9.0 release. Unlike the Guile-based gnunet-setup from 0.8.x, the new tool uses Glade and Gtk+, making it easier for designers to tweak the UI -- and hopefully easier for developers to add auto-configuration features as well, making the "wizard" mode obsolete.

You can grab a copy of the source from

Autonomous NAT Traversal @ P2P 2010

Some GNUnet developers presented a paper co-authored with Samy Kamkar and Andreas Müller this week at P2P 2010 in Delft, The Netherlands. The slides are attached to this post.

The topic presented was a new NAT traversal technique which uses dummy ICMP or UDP packets to punch a hole through NAT boxes. The direct contribution to GNUnet is another method for reaching peers that would be otherwise inaccessible.

GHM Videos online

The last GNU Hackers Meeting had a focus on "building decentralized GNU applications" and video recordings of all talks are now available on

P2P enthusiasts might find the following talks particularly interesting:

GNUnet approved for PowerDeveloper Project

Power provides help, support and resources for developers using the Power and ARM architectures and embedded devices.

In addition to support forums and having a central repository for said developers, they also have Projects which can be applied for that provide additional resources. Some of these resources include hardware, blog space and software repositories.

GNUnet Hackers at the GNU Hackers Meeting

Several GNUnet hackers are attending the GNU Hackers Meeting and giving presentations this weekend. We'll post the presentations here for those who are interested.

Presentations posted below, as follows:

ghm2010.pdf - Christian Grothoff, extended overview of GNUnet including ECRS, GAP and the new 0.9 implementation.

wachs_ghm_presentation.pdf - Matthias Wachs, details about the transport service and plugin structure as well as challenges for intelligent transport selection.

Prüfsummenfehler: Probleme bei gelöschtem hostkey


Unter bestimmten Bedingungen wird gnunetd vor Prüfsummenfehlern in Meldungen warnen, die von anderen Knoten gesendet wurden. Das ist meistens weder ein Softwarefehler, noch ein Problem. Alles funktioniert bestens. Der häufigste Grund ist folgender: jeder Knoten im GNUnet hat einen geheimen und einen öffentlichen Schlüssel. Wenn der gnunetd-Prozeß gestartet wird, schaut er im Verzeichnis date/hosts/ nach, ob dort Schlüssel und Adressen von anderen GNUnet-Knoten gespeichert sind.

Ich bekomme eine Fehlermeldung der Form "Failure at FILE.c:LINE". Was ist los?


Wir benutzen eine generische Fehlermeldung in GNUnet um mitzuteilen, dass etwas schief ging. Der Grund ist normalerweise ein Bug oder Datenbeschädigung im Netzwerk. Beachte, dass der Bug nicht notwendigerweise in der aktuellen Version sein muss -- das Problem könnte von einem anderem Peer verursacht wurden sein, der eine andere Version von GNUnet benutzt. Auch könnte das Problem alles sein, von vollkommen harmlos, bis zu deinen Peer wertlos machend.


Subscribe to GNUnet RSS