|
From: | GNU bug Tracking System |
Subject: | bug#41803: closed ([PATCH] Yggdrasil package and accompanying shepherd service (mesh network)) |
Date: | Thu, 05 Nov 2020 17:49:01 +0000 |
Your message dated Thu, 5 Nov 2020 18:48:08 +0100 with message-id <20201105184808.5464dea4@tachikoma.lepiller.eu> and subject line Re: [bug#41803] [PATCH] Yggdrasil package and accompanying shepherd service (mesh network) has caused the debbugs.gnu.org bug report #41803, regarding [PATCH] Yggdrasil package and accompanying shepherd service (mesh network) to be marked as done. (If you believe you have received this mail in error, please contact help-debbugs@gnu.org.) -- 41803: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=41803 GNU Bug Tracking System Contact help-debbugs@gnu.org with problems
--- Begin Message ---Subject: [PATCH] Yggdrasil package and accompanying shepherd service (mesh network) Date: Thu, 11 Jun 2020 15:56:56 +0200 from: https://yggdrasil-network.github.io/ "Yggdrasil is an early-stage implementation of a fully end-to-end encrypted IPv6 network." I spent the last few days packaging it and now it's in a state where I think it's usable. The configuration can include private keys, so that part should NOT go in the operating system config, because it would get stored in the world-readable Guix store. Nix works around this by merging the generated config with a JSON file and sending it to yggdrasil over its stdin. I chose not to do that because I couldn't figure out how to open a service's stdin and because I think the way I did it is much more elegant in the long run. The package is lightly patched to take not one but two config files, and it simply merges them internally. The patch is completely backwards compatible and unobtrusive. It took me about an hour to write and debug and most of that was just figuring out Go's syntax and type system. I will try to get upstream to accept it, or implement similar functionality. Still TODO: documenting the service as an info page. The gist of using it is: 1. look at example operating system 2. see yggdrasil -genconf -json for config options (3.) optional: save output as /etc/yggdrasil-secret.conf (4.) chmod 600 /etc/yggdrasil-secret.conf (5.) delete everything but the signing and encryption keys 6. add peers as needed, or set autoconf? to #t to connect through a local peer It seems to work fine. I could connect to open peers from one machine and another one could auto-configure itself to connect through the first one over the LAN. It's pretty nifty.0001-gnu-go-golang-org-x-sys-update-to-05986578812163b266.patch
Description: Text Data0002-gnu-add-yggdrasil-dependencies.patch
Description: Text Data0003-gnu-add-yggdrasil-package-at-version-0.3.14-plus-pat.patch
Description: Text Data0004-gnu-services-Add-new-service-for-yggdrasil-network.patch
Description: Text Data0005-gnu-system-add-example-with-yggdrasil.patch
Description: Text Data
--- End Message ---
--- Begin Message ---Subject: Re: [bug#41803] [PATCH] Yggdrasil package and accompanying shepherd service (mesh network) Date: Thu, 5 Nov 2020 18:48:08 +0100 Le Thu, 5 Nov 2020 15:43:41 +0100, raingloom <raingloom@riseup.net> a écrit : > Final version, hopefully. > Slight upgrade to system example to make testing easier. (added curl > to packages) Thank you, finally pushed as 336c9f0a81c9bc0ed0a2d3e0d050a677806c07c0 to fe1cd098d2b83737e96f19438612291f5a9316e4. I had to change a few things: the commit messages need to be written in present tense (Added -> Add). I added some line breaks in the manual and double spacing before periods. I changed the synopsis and description of one or two packages to match our standards.
--- End Message ---
[Prev in Thread] | Current Thread | [Next in Thread] |