On Mon, Apr 29, 2019 at 10:09:11PM +0200, Christian Grothoff wrote: > On 4/29/19 9:48 PM, IC Rainbow wrote: > > Ah, I see. So, I copy that to `share/gnunet/hellos/` and... that would > > give me what? > > Exactly what you wanted: a public key of a peer, an IP address and a > port to connect to for bootstrapping. > > > Is there a handbook section on how to produce and use those files? > > Your peer automatically puts them into > ~/.local/share/gnunet/peerinfo/hosts. > > However, you must apply the 'gnunet-hello' program (NOT installed!) to > them to set the 'expiration' time to 'never' to produce exactly this > type of file, as the auto-generated files come with a (short-ish) > expiration time. And no, I don't think this is documented.
Should we maybe install this tool if it makes sense for normal users? On small systems (OpenWrt, ...) GNUnet is anyway split into a few dozens of packages, one more wouldn't hurt ;) > > > On Mon, Apr 29, 2019 at 10:39 PM Christian Grothoff <[email protected]> > > wrote: > >> > >> Yes, see commit 6ec7797ac937cb7e903688d5743c7debeda115fc. > >> > >> On 4/29/19 9:35 PM, IC Rainbow wrote: > >>> On Sat, Apr 27, 2019 at 8:53 AM Christian Grothoff <[email protected]> > >>> wrote: > >>> > >>>> Yes, there is, except that the pkey we shipped in 0.11.3 (which had been > >>>> stable since 0.9.x) changed unexpectedly. So once we release 0.11.4, > >>>> this will be fixed. > >>> > >>> Is this in master yet? I looked through commits and haven't spotted > >>> any relevant changes. > >>> > >> > > _______________________________________________ > GNUnet-developers mailing list > [email protected] > https://lists.gnu.org/mailman/listinfo/gnunet-developers _______________________________________________ GNUnet-developers mailing list [email protected] https://lists.gnu.org/mailman/listinfo/gnunet-developers
