From mboxrd@z Thu Jan 1 00:00:00 1970 From: ng0 Subject: gnunet-service, first draft in need of review. Date: Mon, 19 Dec 2016 19:30:28 +0000 Message-ID: <20161219193029.10513-1-ng0@libertad.pw> Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:41488) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cJ3e8-0007DP-M1 for guix-devel@gnu.org; Mon, 19 Dec 2016 14:30:53 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cJ3e5-00082r-Id for guix-devel@gnu.org; Mon, 19 Dec 2016 14:30:52 -0500 Received: from aibo.runbox.com ([91.220.196.211]:33167) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1cJ3e5-00082S-CP for guix-devel@gnu.org; Mon, 19 Dec 2016 14:30:49 -0500 Received: from [10.9.9.212] (helo=mailfront12.runbox.com) by bars.runbox.com with esmtp (Exim 4.71) (envelope-from ) id 1cJ3e1-0006ZV-Jy for guix-devel@gnu.org; Mon, 19 Dec 2016 20:30:45 +0100 Received: from exit1.ipredator.se ([197.231.221.211] helo=localhost) by mailfront12.runbox.com with esmtpsa (uid:892961 ) (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) id 1cJ3dl-0001jJ-VE for guix-devel@gnu.org; Mon, 19 Dec 2016 20:30:30 +0100 List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: guix-devel@gnu.org Hi, I picked up the service I started working on in september. In some parts I'm picking a starting point now with what I already worked on in the past, file:net-misc/gnunet/files/gnunet.initd visible at https://gnunet.org/git/youbroketheinternet-overlay.git/ specifically with the setuid parts. I'm pretty sure that the setuid thing was removed in a later revision, but (sadly) I have to deal with this terrible old checkout which is 0.10.1 for reasons. I'd like someone to review the shepherd service so I can be sure that the errors I'm getting aren't gnunet related. You have to configure a system (didn't test VMs) with this patch. gnunet will fail to start, and then you have to "sudo shepherd start gnunet". Your user can get added to the now existing gnunet group, which is the upstream intended way to use gnunet (or one of the ways) with one system user/group and users belonging to the group to start/execute the binaries.