Re: What's a simple way to set up a private network of a few peers for testing purposes?

2021-09-23 Thread Christian Grothoff
Why don't you just run a few VMs on your local machine? It's not like a GNUnet peer requires tons of resources, so a typical system should easily be able to run several VMs with a GNUnet peer in each. If you then disable external network connectivity, you're pretty much guaranteed to only be talkin

Re: Open questions regarding new messenger and secushare and organization Was: Make GNUnet Great Again

2021-09-23 Thread t3sserakt
You do not need to move those conf files! The content of those files is the default configuration used by GNUnet if you have a empty config file. Every configuration option you like to chance from its default behavior has to be written into the config file which will overwrite the default be

Re: Open questions regarding new messenger and secushare and organization Was: Make GNUnet Great Again

2021-09-23 Thread Tobias Platen
First I moved to config files to the right place, then I ran "gnunet-arm -s". So I have to update the config files to remove the UNIXONLY stuff. sudo mv ./share/gnunet-secushare/config.d/multicast.conf /usr/local/share/gnunet/config.d sudo mv ./share/gnunet-secushare/config.d/psycstore.conf /usr/l

What's a simple way to set up a private network of a few peers for testing purposes?

2021-09-23 Thread Alessio Vanni
Hello, as per the subject, I'm looking for a way to set up a small independent network of peers to test an application. What I'm looking for is primarily for this network to exist independently from the normal global GNUnet network that peers connect to when using the default configuration. I do

Re: Planning to continue working on Secushare

2021-09-23 Thread TheJackiMonster
On Thu, 2021-09-23 at 11:39 +0200, carlo von lynX wrote: > On Thu, Sep 23, 2021 at 11:05:06AM +0200, carlo von lynX wrote: > > The circular topology of end points *does* satisfy the secushare > > expectations on privacy and metadata privacy in particular AFAICT, > > so that's very cool. > > Whoops

Re: Planning to continue working on Secushare

2021-09-23 Thread carlo von lynX
On Thu, Sep 23, 2021 at 11:05:06AM +0200, carlo von lynX wrote: > The circular topology of end points *does* satisfy the secushare > expectations on privacy and metadata privacy in particular AFAICT, > so that's very cool. Whoopsa I'm posting faster than I am thinking, sorry. No, without any form

Re: Planning to continue working on Secushare

2021-09-23 Thread carlo von lynX
On Thu, Sep 23, 2021 at 10:29:02AM +0200, TheJackiMonster wrote: > Because the messenger service was mentioned I thought I could try to > clarify. I'm unsure if it's the proper back-end for secushare but > technically speaking you can just think of it as layer on top of CADET > to form groups using

Re: Planning to continue working on Secushare

2021-09-23 Thread TheJackiMonster
Because the messenger service was mentioned I thought I could try to clarify. I'm unsure if it's the proper back-end for secushare but technically speaking you can just think of it as layer on top of CADET to form groups using a shared secret without necessary centralization. The latency and stabi

Re: Planning to continue working on Secushare

2021-09-23 Thread carlo von lynX
Tobias, so happy to hear that your hands-on on the matter! Everything t3sserakt warns about is unfortunately true - after all the effort put into those subsystems we don't know if they have a chance of delivering what we need at any happy point in the future. Some additional thoughts on what t3sser

Re: Planning to continue working on Secushare

2021-09-23 Thread t3sserakt
Hey Tobias, On 19.09.21 11:08, Tobias Platen wrote: > I successfully compiled gnunet-secushare, but I got an a runtime error, > so the next thing that I'll do ist fixing many bugs that occur. > > 2021-09-19T10:57:50.884585+0200 gnunet-social-110956 ERROR Assertion > failed at social_api.c:2682. Ab