Ask your questions here.
Post a reply
nadir

- nadir
- Posts: 1160
- Joined: Wed Mar 09, 2011 4:18 am
- Location: here

## gnunet

Sun Aug 11, 2013 12:20 am

After a break i looked into gnunet again.
Again i failed, but more miserably than before.
Anyone has a) experience or b)interest in it?
btw: This video made me look at it again (someone posted it somewhere on the internet):
https://gnunet.org/internetistschuld
The video is interesting.
In IRC they told me a) it's not ready for users yet (but i really would like to run it) and b) to use the tar.gz version ( i failed miserably) and to c) ask again when the dev is there (will do that).
nadir

- nadir
- Posts: 1160
- Joined: Wed Mar 09, 2011 4:18 am
- Location: here

## Re: gnunet

Mon Aug 12, 2013 12:10 am

I will not go into detail, because i can't. But i can give a very few hints of the things i have figured out yet (by docu and IRC and more).
1) You will want to use the upstream source and compile it in the configure/make/make-install routine
2) Before you download or do so, add a user called gnunet and a group called gnunetdns
addgroup gnunetdns
adduser gnunet
Download the tar.gz as user gnunet and run the commands as user gnunet.
3) The official docu says to configure with a weird syntax (or path), and here it is:
./configure --prefix=$HOME --with-extractor=$HOME
extractor is in the debian repos, so i skipped that:
./configure --prefix=$HOME --with-extractor=$HOME
The result is, to put it mildly, odd (bin and include and lib and share in /home/
4) If you also plan to install gnunet-gtk, you will have to
PKG_CONFIG_PATH=/home/gnunet/lib/pkgconfig
export PKG_CONFIG_PATH
then run ./configure $prefix=$HOME
There are a few hints about /home/gnunet/.gnunet/gnunet.conf at:
https://gnunet.org/configuration-hostlist
but they are spread all over the docu.
gnunet-arm -s #should start it
gnunet-arm -e #should stop it
gnunet-core #and
gnunet-peerinfo -i # should give you some info if you are connected at all.
nadir

- nadir
- Posts: 1160
- Joined: Wed Mar 09, 2011 4:18 am
- Location: here

## Re: gnunet

Mon Aug 12, 2013 12:11 am

Ah, well, here is the final info of ./configure, which made things slightly more clear to me:

> configure: ********************************************
> Please make sure NOW that you have created a user and group 'gnunet'
> and additionally a group 'gnunetdns':
> addgroup gnunetdns
> adduser gnunet
> Make sure that '/var/lib/gnunet' is owned (and writable) by user
> 'gnunet'. Then, you can compile GNUnet with
> make
> After that, run (if necessary as 'root')
> make install
> to install everything.
> Each GNUnet user should be added to the 'gnunet' group (may
> require fresh login to come into effect):
> adduser gnunet
> (run the above command as root once for each of your users, replacing
> "" with the respective login names). If you have a global IP
> address, no further configuration is required.
> Optionally, download and compile gnunet-gtk to get a GUI for
> file-sharing and configuration. This is particularly recommended
> if your network setup is non-trivial, as gnunet-setup can be
> used to test in the GUI if your network configuration is working.
> gnunet-setup should be run as the "gnunet" user under X. As it
> does very little with the network, running it as "root" is likely
> also harmless. You can also run it as a normal user, but then
> you have to copy ~/.gnunet/gnunet.conf" over to the "gnunet" user's
> home directory in the end.
> Once you have configured your peer, run (as the 'gnunet' user)
> gnunet-arm -s
> to start the peer. You can then run the various GNUnet-tools as
> your "normal" user (who should only be in the group 'gnunet').
> ********************************************

I would have needed the info _before installing it.
nadir

- nadir
- Posts: 1160
- Joined: Wed Mar 09, 2011 4:18 am
- Location: here

## Re: gnunet

Mon Aug 12, 2013 2:41 pm

https://gnunet.org/content/project-status-august-2013
For what reason ever, here is the content:

> Mon, 08/12/2013 - 09:43 — Christian Grothoff
> As there seems to be some larger number of people recently looking at GNUnet, Krista convinced me to elaborate on the current state of the system so that newcommers quickly get an appropriate idea of where we are right now. The short version is this: GNUnet is not yet ready for production use.
> Where are we?
> We're currently in a phase where we are making some radical changes to the protocol with respect to the previous release. As a result, protocol incompatibilities ensure that the network remains tiny. Some of the changes include moving from RSA to ECC/ECDHE, and most recently changing timer resolution from milliseconds to microseconds (which affects signatures as they include timestamps). In the wake of such high-level breakage, we're also fixing various protocol issues deeper in the bowls of the system.
> We are still waiting for ED25519 support in libgcrypt (we're currently using NIST-256, but the goal is to move to ED25519 before the protocol transition is considered finished), the GNU Name System crypto still has some changes that need to be implemented, and the mesh layer protocol implementation also is still incomplete. Once these are done and we're no longer aware of major bugs, we'll release GNUnet 0.10 and hopefully not touch the protocols like this for a long time (some of the stuff we're changing this time was in place since GNUnet 0.0.0, so this is major housecleaning).
> After that, we expect that file-sharing and GNS (our DNS replacement) will work nicely. Shortly after that, the plan is to polish the VPN (especially configuration is currently a *****), release GNUnet 1.0 and then the development focus will shift more towards social applications (SecuShare, PSYC, etc.). Features such as improvements to performance, NAT traversal, configuration, documentation and others are happening as well, but they are not tied to the main roadmap and will simply be deployed whenever they are ready.
> What can you run today?
> Some distributions package GNUnet 0.8. That's so ancient I won't even talk about it. The only versions that might give you any reasonable impression of where we are, are 0.9.5a and SVN HEAD. For SVN HEAD, you will also need to clone libgcrypt from Git, as libgcrypt 1.5.x is not recent enough. In 0.9.5a quite a few things used to work (file-sharing, GADS, on GNU/Linux also VPN/PT); however, the network is very small right now (think a dozen peers, if you're lucky), and some of the hostlists servers are down so you might not find those that are left. Also, 0.9.5a is not protocol compatible with SVN HEAD. Still, you can play around with the GUIs, look at the C APIs, use the command-line tools to see what your peer is doing, or run a network with a few thousand peers on loopback on a normal desktop.
> SVN HEAD is likely incompatible with yesterday's version of SVN HEAD, so the network will be even smaller. On the bright side, you get improved crypto, improved APIs, some new features and nicer GUIs. So if you want to see what is around the corner or hack with us, that's what you want to try. But again, this is not ready for your mom just yet.
> How can you help?
> A good starting point is our bugtracker. You can also help by making sure that when you ask questions (for example, on IRC), the answers are documented. So if you read our documentation and have trouble understanding it, please feel free to ask us, but then help us by providing patches to the documentation so that others won't need to ask the same questions again. You're also welcome to help with translating the documentation to other languages; if you have done some translations, please contact us directly so we can host them on gnunet.org. We are aware that documentation --- especially for normal users --- is so far very sparse and needs to be improved. So help in this area is particularly welcome.

nadir

- nadir
- Posts: 1160
- Joined: Wed Mar 09, 2011 4:18 am
- Location: here

## Re: gnunet

Tue Aug 13, 2013 12:25 am

First draft.
Too chatty.
Main part is how to compile, _after creating gnunet user and group gnunetdns, not setting up the peer.
build-from-source
=================
Created Tuesday 13 August 2013
Overview:
1) create user gnunet and group gnunetdns
2) install the dependencies for building
3) compile gnunet
4) compile gnunet-gtk
5) edit gnunet.conf
6) add further users to the group gnunet
7) tips
--- 1) prepare: create user and group ---
$ su
# adduser gnunet
# addgroup gnunetdns
- dependencies -
https://gnunet.org/dependencies
and/or use the output of errors from ./configure.
It seems to be sufficient for gnunet and gnunet-gtk, but i already have lots of tools installed.
--- 2) become user gnunet, get the code and compile ---
# su - gnunet
$ cd
$ mkdir Build
$ cd Build
download links:
https://gnunet.org/downloads
- gnunet -
mkdir gnunet
$ wget ftp://ftp.gnu.org/gnu/gnunet/gnunet-0.9.5a.tar.gz
$ tar xzf gnunet-0.9.5a.tar.gz
$ cd gnunet-0.9.5a
$ ./configure --prefix=$HOME
$ make
$ su
# make install # to /home/gnunet/{bin,include,lib,share}
# exit
--- 3) gnunet-fs-gtk ---
$ cd /home/gnunet/Build
$ mkdir gnunet-gtk
$ wget ftp://ftp.gnu.org/gnu/gnunet/gnunet-gtk-0.9.5.tar.gz
$ tar -xzf gnunet-gtk-0.9.5
$ cd gnunet-gtk-0.9.5
$ ./configure --prefix=$HOME
- will complain about PKG_CONFIG_PATH; fix it with:
$ PKG_CONFIG_PATH=/home/gnunet/lib/pkgconfig/
$ export PKG_CONFIG_PATH
- will complain next about missing GNUnet core utils, fix it with
$ apt-get install gnunet-dev
$ make
$ su
# make install
Now remove gnunet installed with apt-get again. There will be problems with gnunet-server, postrm errors. Do
rm /var/lib/dpkg/info/gnunet*
and then
apt-get remove --purge gnunet-server
The rest (gnunet-common, gnunet-client, etc) remove like usual.
#exit #root
—- 4) gnunet.conf ---
create and edit:
/home/gnunet/.gnunet/gnunet.conf
[hostlist]
OPTIONS = -b -e
SERVERS = http://v9.gnunet.org:58080/
HOSTLISTFILE = $SERVICEHOME/hostlists.file
More here:
https://gnunet.org/configuration-hostlist
--- 5) final setup; tips ---
source .profile
as user gnunet, to introduce ~/bin with all gnunet* commands to your shell (or log out and back in as user gnunet, duh
gnunet-arm -s #to start
gnunet-arm -e #to stop
exit user gnunet, and as your normal user run:
sux - gnunet
Now run gnunet-setup, the graphical setup tool:
gnunet-setup
You are probably using NAT. Go to the network tab and click on it. If possible open the port(s): 2086 and, not sure, 1080 (not sure if that is needed).
Close gnunet-setup.
To check if you are integrated, do:
gnunet-core
gnunet-peerinfo
To start the gui run (again, you will need sux):
gnunet-fs-gtk
Add other users to the gnunet group, as root do:
# adduser username gnunet
(like usual, log out and back in).
nadir

- nadir
- Posts: 1160
- Joined: Wed Mar 09, 2011 4:18 am
- Location: here

## Re: gnunet

Sat Aug 17, 2013 12:32 am

It seems to work, but i got no idea what to do with it.
Downloading the example file (GPL) worked, downloading music failed.
If someone installs it himself (for the fun of it) we may try to copy stuff from-to (aka back and forth), i uploaded a few example music files (perhaps text, as it's smaller, is a better idea).
Post a reply
Jump to:

Powered by phpBB © phpBB Group.

phpBB Mobile / SEO by Artodia.