Re: Fedora Packaging: gethostbyname

Hello Benson, note that we already have a fedora COPR: https://copr.fedorainfracloud.org/coprs/schanzen/gnunet Here is the upstream issue: https://bugzilla.redhat.com/show_bug.cgi?id=2094246 That being said, patches are always welcome, but I think the nits are not critical due to what

GNUnet 0.21.0 released

We are pleased to announce the release of GNUnet 0.21.0. GNUnet is an alternative network stack for building secure, decentralized and privacy-preserving distributed applications. Our goal is to replace the old insecure Internet protocol stack. Starting from an application for secure

Re: GNUnet 0.21.0 released

Hi, On 07.03.24 14:09, bastianschm...@danwin1210.de wrote: Hello, first of all, GNUnet 0.21.0 - finally brought to this part of the multiverse, that's a biggy. Lots of important work went into it for reaching this point - among others integration of TNG, right? Virtual applause to all devs

Re: gnunet-gtk GTK4 port

Well I think at least the use of cambalache would imply the use of libadwaita as well. Br Martin On 06.03.24 08:20, Gotam Gorabh wrote: Hello, I would like to know if we plan to use *Libadwaita* during the porting process. After that I will prepare my GSoC proposal accordingly. BR Thanks

Re:

Hi, first of all, this is the primary GSoC issue: https://bugs.gnunet.org/view.php?id=5679 There are unfortunately no gnunet-gtk issues to point to I think. This is the full list: https://bugs.gnunet.org/view_all_bug_page.php But, I am not sure how many of those actually still apply. Maybe

Re: GSoC 2024: gnunet-gtk gtk4 upgrade

very strongly recommend using Cambalance --- and to use the opportunity to clean up the GUIs ;-). On 2/27/24 20:51, Schanzenbach, Martin wrote: I think our use of glade is historical. It just made sense to somebody (not me, my guess is Christian). I personally have no issue with moving away from

Re: GSoC 2024: gnunet-gtk gtk4 upgrade

Try exporting GNUNET_PREFIX: You may have provided "--prefix=" to configure. If you did not, it is "/usr/local". Before you run gnunet-gtk, run: $ export GNUNET_PREFIX=/lib Br On 28.02.24 05:52, Gotam Gorabh wrote: Hey, I built and installed *gnunet* and *gnunet-gtk *successfully**but

Re: GSoC 2024: gnunet-gtk gtk4 upgrade

I think our use of glade is historical. It just made sense to somebody (not me, my guess is Christian). I personally have no issue with moving away from glade as RAD tool as I find it very cumbersome myself. Note, however, that it will also mean writing a lot of code that is currently hidden

Re: Interacting with other peers

Yes, you can use the MQ from the ConnectEventHandler to send a message to the connected peer (s). You know that you have to throw the peer/MQ away when the DisconnectEventHandler is called. BR Martin On 27.02.24 11:39, Andrei Ușurelu wrote: By using the CORE service I mean fetching each peer

Recent peerstore changes in git head

Hello, due to recent changes in the peerstore DB layout, you will need to purge your old peerstore sqlite.db file found (probably) in $HOME/.local/share/gnunet/peerstore/sqlite.db Otherwise, your peerstore will fail to start. BR

Re: FS replication level

Hi, the replication level defines to what degree a degree the data is (redundantly) replicated. Say, at replication level 0 your file is divided into blocks, exactly 1 peer would be authoritative in the DHT for that block and store it. With a replication level of 1, one additional peer is

Re: GNUnet Monthly Meeting Sunday, 3rd December, 8 PM Paris/Berlin/Rome

I don't even think that was malicious. Somebody just used a translator. Well, that's the tradeoff for using a public pad... But, if we wanted to actually preserve the minutes we would check them into the git, so it's whatever. BR On 11.12.23 17:16, Marcos Marado wrote: Hi there, FYI, it

Re: GNUnet Name System Questions

I'm sorry I do not understand the question. How does any of this relate to GNS? Best Martin On 03.12.23 09:56, retrovirus-...@juno.com wrote: I almost forget to mention that there is a possible issue with URL https://IPv4_IP_address and https://[IPv6_IP_address]. SSL certification, at least

Re: GNUnet Name System Questions

There is a first-come-first-served registrar for .pin subdomain which is a history service by the gnunet project. Any zone owner can potentially act as a zone registrar and sell (or give away) subdomains. We are currently working on a new registrar service that will also be integrated with

Re: RFC 9498: The GNU Name System

Hi, On 21.11.23 18:55, Maxime Devos wrote: Op 21-11-2023 om 08:34 schreef Schanzenbach, Martin: We are happy to announce that our *The GNU Name System* (GNS) specification is now published as RFC 9498 [0]. in order to transparently enable this functionality for migration purposes, a local

RFC 9498: The GNU Name System

We are happy to announce that our *The GNU Name System* (GNS) specification is now published as RFC 9498 [0]. GNS addresses long-standing security [1] and privacy [2] issues in the ubiquitous Domain Name System (DNS) [3]. Previous attempts to secure DNS (DNSSEC [4]) fail to address critical

RFC 9498: The GNU Name System

We are happy to announce that our *The GNU Name System* (GNS) specification is now published as RFC 9498 [0]. GNS addresses long-standing security [1] and privacy [2] issues in the ubiquitous Domain Name System (DNS) [3]. Previous attempts to secure DNS (DNSSEC [4]) fail to address critical

Re: GNUnet 0.20.0 released

Still, writing both the email AND the news post is tedious, so it would be nice to only write it once, from a template, and then generate both. Or generate one out of the other, without having to actually send HTML email. That being said, I would actually prefer to only send the link to the

Re: purge_secrets missing return on non-void function

Hi, it is thanks. I just fixed it in git head. BR Martin On 25.09.23 14:18, Andreas Stieger wrote: Hello, I am not sure if this is new as of 0.20.0 or earlier, but this seems to be related to bb4036: [   50s] gnunet-communicator-udp.c: In function 'purge_secrets': [   50s]

Re: Adding generic cryptographic self-authenticating block on DHT

More info: The registry is in the docs: https://docs.gnunet.org/gana/gnu_name_system_record_types.html and you probably want to use this for GNS: https://docs.gnunet.org/developers/subsystems/gnsstack.html Am 28.05.23 um 17:11 schrieb Schanzenbach, Martin: Hi! Am 28.05.23 um 11:17 schrieb

Re: Adding generic cryptographic self-authenticating block on DHT

Hi! Am 28.05.23 um 11:17 schrieb marty1885: Hi, I've been working on my own to build a private messaging system on GNUnet (just for fun, as a hobby project). It's not exactly the same as libgnunetchat. My goal is to create a system that works like email and supports message delivery even when

Re: Another GNUnet Project GSOC 2023 Contributor

Hi Igor, sounds good. Try running $ ldconfig or (if you have GNUnet installed in $GNUNET_PREFIX) $ export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$GNUNET_PREFIX and see if that fixes the problem. Best Martin Am 22.03.23 um 00:25 schrieb Игорь Антонов: Hi GNUnet developers! Just like Marshall

Re: Hello from the libp2p project

Hi Max, thanks for reaching out. Indeed, it would be great to establish an exchange between our projects. There are actually a few ideas floating around already in my head, but due to lack of time there is little chance that I will take a serious myself in the near future such as a GNS

Re: About GNUrl and cURL

commited a programmatic check for GnuTLS. Try it out. It should > > > > not > > > > require your fix. > > > > > > > > Mmm without my trick the configure script still prints > > > > > > > > ... > > > > HTTP Client:

Re: A more general question about curl

rectly wget2 introduced non-blocking sockets. That's all I > know. I did not find a lot of info on Google, except maybe for this email on > gnutls mailing list: > https://lists.gnutls.org/pipermail/gnutls-devel/2019-June/014051.html > > --madmurphy > > On Wed, Sep 7, 202

Re: About GNUrl and cURL

> On 7. Sep 2022, at 14:59, madmurphy wrote: > > Hi Martin, > > That means, if you can find out how the packages linked against > libcurl-compat or libcurl-gnutls are built from source, you can do the same > with the gnunet package. > The packages in the official repositories that

Re: A more general question about curl

We need a non-blocking API such as curl_multi. Last time I checked, libwget2 does not have that. BR > On 7. Sep 2022, at 15:46, madmurphy wrote: > > I don't know all the reasons behind using curl and all GNUnet's requirements, > but have you guys thought about switching to wget2? It is a GNU

Re: About GNUrl and cURL

ibcurl-gnutls. BR > > On Tue, Sep 6, 2022 at 1:47 PM madmurphy wrote: > I will try to check the configure.ac file. I don't get an error btw, only > that "curl-openssl" http client... > > On Tue, Sep 6, 2022 at 1:45 PM Schanzenbach, Martin > wrote: &g

Re: About GNUrl and cURL

t; Happy hacking > Jacki > > On Tue, 2022-09-06 at 17:16 +, Schanzenbach, Martin wrote: >> I know why this does not work for you. >> For example, in debian, there is a libcurl4-gnutls-dev which includes >> the ".so" file. >> That arch package

Re: About GNUrl and cURL

I know why this does not work for you. For example, in debian, there is a libcurl4-gnutls-dev which includes the ".so" file. That arch package is missing the (_unversioned_) ".so" file. I do not know if there is a "-dev" equivalent in arch. BR > On 6. Sep 202

Re: About GNUrl and cURL

intelligent with respect to curl-gnutls > detection. > > BR > > Excerpts from Schanzenbach, Martin's message of 2022-09-06 08:59:23 +: > > Ah sorry I just checked: > > If "normal" curl is found, the check for curl-gnutls is skipped. > > I guess we

Re: About GNUrl and cURL

ld prefer curl-gnutls. > Yes, libcurl-gnutls should be checked first. Also because apparently Arch is > not the only distro that has a split package of cURL linked against GNU TLS… > > --madmurphy > > > On Tue, Sep 6, 2022 at 9:59 AM Schanzenbach, Martin > wrote: > Ah sorry

Re: About GNUrl and cURL

Ah sorry I just checked: If "normal" curl is found, the check for curl-gnutls is skipped. I guess we should prefer curl-gnutls. Br > On 6. Sep 2022, at 10:51, Schanzenbach, Martin > wrote: > > Hi, > > check your config.log and check for the test against libcurl-gn

Re: About GNUrl and cURL

Hi, check your config.log and check for the test against libcurl-gnutls. There should be test somewhere in there that fails for reasons. BR Martin > On 5. Sep 2022, at 20:21, madmurphy wrote: > > Hi Christian, > > I tried to run ./configure twice. The first time I had installed on my >

Re: Help - curl must support CURLINFO_TLS_SESSION

Hi, yes this is an issue with a deprecation in the most recent curl release. This is fixed in git master, I hope. And in the next release. BR > On 3. Sep 2022, at 16:15, Nirvin M wrote: > > Dear GNUnet developers, > > I tried compiling gnunet on latest stable versions of Fedora and Debian,

Re: Help needed with compilation

Hi Nirvin, did you follow the instructions and ran $ ./bootstrap and $ ./configure ... ? If yes, maybe did they fail? If so, you need to fix the error first. Possibly by installing missing dependencies. Br Martin > On 1. Sep 2022, at 13:20, Nirvin M wrote: > > Hello GNUnet developers, > >

Re: Question about tracking files, and Doxygen updates.

nunet.org/view.php?id=7314) where we can > coordinate clearing redundant Doxygen comments. It's lighter work now, but a > helping hand wouldn't go amiss. > > Best wishes, > Willow > > On 28/08/2022 09:06, Schanzenbach, Martin wrote: >>> On 28. Aug 2022, at 00

Re: Question about tracking files, and Doxygen updates.

> On 26. Aug 2022, at 23:41, Willow Liquorice wrote: > > Hello again, > > I've put a .gitignore in doc/doxygen on my local dev/willow/doxygen, so the > Doxygen output (along with other autogenerated files) doesn't get tangled up > in the git history. Should .gitignore include gnunet.tag

Re: Commit messages and rebasing

Hi Willow, thank you. I rebased and merged your branches to master BR Martin > On 21. Aug 2022, at 00:05, Willow Liquorice wrote: > > Hello again, > > I got to tidying up the commit history on dev/willow/gnunet_temp, those > changes should be reflected on the remotes. I've also rebased and

Re: gnunet-go R5N

> On 18. Aug 2022, at 15:20, Maxime Devos wrote: > > On 18-08-2022 15:10, Bernd Fix wrote: > >> A new version (v0.1.32) of gnunet-go is availble at >> https://git.gnunet.org/gnunet-go.git that should be ready for integration >> tests. Some major and minor bugs have been fixed that have

Re: LSD uses Google Fonts

Thanks I borrowed this solution from you :) > On 13. Jul 2022, at 09:00, pukkamustard wrote: > > > Hi GNUnet, > > The LSD documents as published at https://lsd.gnunet.org currently use > Google Fonts. This is due to the default stylesheet used by the xml2rfc > tool. > > I think there has

Re: Attacking the documentation monster

guration they use to perform the navigation. Would anyone like to see > them? > Sounds like something that may go somewhere into contrib (the lua script/nvim config). For now, I would like to tackle the handbook first. BR Martin > Best wishes, > Willow Liquorice > > On

GNUnet services and GNS

Hi, we now publish (some) GNUnet service IPs in GNS through in zone 000G0047M3HN599H57MPXZK4VB59SWK4M9NRD68E1JQFY3RWAHDMKAPN30. This will become a default configuration in the upcoming releases. For now, you can configure it like this: $ gnunet-config -s gns -o ".gnunet.org" -V

Re: Attacking the documentation monster

Hi, I was wondering if you had started with sphinx/rtd for the handbook already? If not, I have played around with it today and already have migrated some text and could commit it to gnunet.git or a new repo. That would allow anyone to play around and add content. But if you are already further,

Re: Packaging problems

> On 3. Jun 2022, at 21:44, Christian Grothoff wrote: > > Having many packages doesn't usually make it easier for packagers, it just > means that now they have to deal with even more sources, and create more > package specifications. Moreover, build times go up, as you now need to run >

Re: GNUnet Monthly Meeting Sunday, 1st May, 8 PM CET

We could just always move it to UTC+1 (=CET) while we are at it. > On 26. Apr 2022, at 18:37, hyazin...@emailn.de wrote: > > *sigh* CEST—summer time—of course, not CET. > Sorry for that. I have put better measures in place for avoiding this mistake > in the future. > > --- Ursprüngliche

Re: gnunet-rest-server shutdown issues

is coming from. The cleanup logic looks ok. If the log message appears after the SIGKILL then I need to investigate a bit further, but it may be a signal handler issue. BR > On 11. Apr 2022, at 13:46, Nikita Ronja Gillmann wrote: > > Hi, > > Schanzenbach, Martin transcribed 4

Re: gnunet-rest-server shutdown issues

-11T08:17:11.374183+0200 namestore-656 ERROR Assertion failed at >> plugin_namestore_sqlite.c:537. >> 2022-04-11T08:17:11.374232+0200 namestore-656 ERROR Assertion failed at >> gnunet-service-namestore.c:1949. >> >> looks like there is some issue related to accessing in

Re: GNUnet Name System not working (as expected)

> On 11. Apr 2022, at 09:13, Tanguy LE CARROUR wrote: > > Hi Martin, > > > Quoting Schanzenbach, Martin (2022-04-09 10:27:56) >>> On 8. Apr 2022, at 16:02, Tanguy LE CARROUR wrote: >>> Quoting Nikita Ronja Gillmann (2022-04-08 12:29:43) >>&

Re: gnunet-rest-server shutdown issues

Hi, this is not a known bug and it would be very odd if the REST API is not even used. So yes, debug logs would be helpful. BR > On 10. Apr 2022, at 22:31, Nikita Ronja Gillmann wrote: > > Hi, > > in my system service I have a pill + kill for gnunet-rest-server, > as this process seems to

Re: mysql check always fails

nt 8.0.24. > > The patch I use fixes the version detection for me. > > Schanzenbach, Martin transcribed 2.6K bytes: >> Can anyone of you open a bug report for this with a description. >> From the mails I do not understand the problem beyond "the check does not >> wor

Re: mysql check always fails

Can anyone of you open a bug report for this with a description. From the mails I do not understand the problem beyond "the check does not work". I can look at it next week. BR Martin > On 8. Apr 2022, at 10:04, Nikita Ronja Gillmann wrote: > > Daniel Golle transcribed 0.7K bytes: >> Hi

Re: GNUnet Name System not working (as expected)

> On 8. Apr 2022, at 16:02, Tanguy LE CARROUR wrote: > > Hi Nikita, > > > Quoting Nikita Ronja Gillmann (2022-04-08 12:29:43) >> Tanguy LE CARROUR transcribed 6.2K bytes: >>> Hello GNUnet, >>> >>> I'm not reporting this into the bug tracker (yet), because (good) chances >>> are the problem

Re: gnurl CVE applicability

> On 4. Apr 2022, at 17:35, Mikhail wrote: > > On Mon, Apr 04, 2022 at 05:14:53PM +0200, Christian Grothoff wrote: >> On 4/4/22 17:09, Nikita Ronja Gillmann wrote: >>> Regardless, you should be able to build GNUnet against vanilla libcurl these days, so that might be a better

Re: gnurl CVE applicability

> On 4. Apr 2022, at 17:14, Christian Grothoff wrote: > > On 4/4/22 17:09, Nikita Ronja Gillmann wrote: >>> >>> Regardless, you should be able to build GNUnet against vanilla libcurl >>> these days, so that might be a better way to avoid worrying about this. >> In the context of pkgsrc, the

Re: openbsd - gnunet warnings in logs

Hi, > On 4. Apr 2022, at 12:32, Mikhail wrote: > > I've installed latest in git (60e93b8f0) on the OS, I didn't use > --prefix, so installation has gone to default /usr/local, when I run > gnunet-peerinfo I see several types of warnings in the logs. > > I'd like to package gnunet for OpenBSD,

Re: compiling gnunet 0.16.3 on openbsd

holds a solution on how to solve this for gnunet. > > On 4/1/22 09:05, Mikhail wrote: >> On Thu, Mar 31, 2022 at 06:58:55PM +, Schanzenbach, Martin wrote: >>> Hi Mikhail, >>> >>> I just pushed some portability fixes to git master. >>> I tried

Re: compiling gnunet 0.16.3 on openbsd

Martin > On 31. Mar 2022, at 18:29, Mikhail wrote: > > On Wed, Mar 30, 2022 at 10:17:32PM +0300, Mikhail wrote: >> On Wed, Mar 30, 2022 at 05:40:53PM +0000, Schanzenbach, Martin wrote: >>> Interesting. I think this hit us: >>> https://bugs.freedesktop.org/show_

Re: compiling gnunet 0.16.3 on openbsd

e a usable openbsd installation. BR > On 30. Mar 2022, at 19:26, Mikhail wrote: > > On Wed, Mar 30, 2022 at 05:16:59PM +, Schanzenbach, Martin wrote: >> Hi, >> >> your configure output does not indicate that LDFLAGS is correctly set >> of your

Re: compiling gnunet 0.16.3 on openbsd

Hi, your configure output does not indicate that LDFLAGS is correctly set of your system libraries are found in /usr/lib Can you try: $ ./configure <..your options> LDFLAGS="$LDFLAGS -L/usr/lib" and see if that works? BR > On 30. Mar 2022, at 19:01, Mikhail wrote: > > Hello, I'm interested

GNUnet 0.16.3 released

Hi, we just released a bugfix release for GNUnet 0.16.2: https://www.gnunet.org/en/news/2022-03-0.16.3.html Best Martin signature.asc Description: Message signed with OpenPGP

GNUnet 0.16.2 released

Hi, we just released a bugfix release for GNUnet 0.16.1: https://www.gnunet.org/en/news/2022-03-0.16.2.html Best Martin signature.asc Description: Message signed with OpenPGP

GNUnet 0.16.1 released

Hi, we just released a bugfix release for GNUnet 0.16.1: https://www.gnunet.org/en/news/2022-03-0.16.1.html Best Martin signature.asc Description: Message signed with OpenPGP

Re: Reducing the number of executables to one

> On 3. Mar 2022, at 01:51, madmurphy wrote: > > Hi Christian, > > As I said, it is more of a long term planning. The main argument in favor is > that (hopefully!) the number of “gnunet-XXX” utilities is only destined to > grow, so eventually at some point it will be needed anyway. I can

GNUnet 0.16.0 released

We are pleased to announce the release of GNUnet 0.16.0. This is a new major release. It breaks protocol compatibility with the 0.15.x versions. Please be aware that Git master is thus henceforth (and has been for a while) INCOMPATIBLE with the 0.15.x GNUnet network, and interactions between

Re: Tutorial - Git repo

> On 17. Feb 2022, at 13:02, Gavin Henry wrote: > > No problem Martin. > > Just looking through all the Peer Discovery code and NAT busting > things for adding the P2P bits to SentryPeer vs what Zyre can do with > OpenDHT. I need to figure out how a peer node can be reached and pop > that

Re: Tutorial - Git repo

Thanks Gavin, fixed, should be deployed soonish. BR Martin > On 17. Feb 2022, at 12:13, Gavin Henry wrote: > > Hi all, > > The docs here > https://docs.gnunet.org/tutorial/tutorial.html#Obtaining-the-latest-version-from-Git > state: > >$ git clone https://git.gnunet.org/gnunet > > so

Re: LSD0001 review

> On 10. Feb 2022, at 23:26, Maxime Devos wrote: > > Schanzenbach, Martin schreef op ma 07-02-2022 om 19:02 [+]: >>>> LEGACY HOSTNAME >>>> A UTF-8 string (which is not 0-terminated) representing the >>>> legacy hostname. >>> >

Re: LSD0001 review

> On 10. Feb 2022, at 23:02, Maxime Devos wrote: > > Schanzenbach, Martin schreef op ma 07-02-2022 om 19:02 [+]: >>>> NICKNAME >>>> >>>>A UTF-8 string (which is not 0-terminated) representing the >>>> preferred label of th

Re: LSD0001 review

> On 7. Feb 2022, at 20:02, Schanzenbach, Martin > wrote: > > > >> On 7. Feb 2022, at 12:37, Maxime Devos wrote: >> >> Hi, >> >>> Name >>> A name in GNS is a domain name as defined in [RFC8499] as an >>> ordered list of

Re: LSD0001 review

> On 7. Feb 2022, at 20:12, Maxime Devos wrote: > > Schanzenbach, Martin schreef op ma 07-02-2022 om 19:02 [+]: >>>> LEGACY HOSTNAME >>>> A UTF-8 string (which is not 0-terminated) representing the >>>> legacy hostname. >>> >

Re: LSD0001 review

> On 7. Feb 2022, at 12:37, Maxime Devos wrote: > > Hi, > >> Name >>A name in GNS is a domain name as defined in [RFC8499] as an >> ordered list of labels. The labels in a name are separated using the >> character "." (dot). Names, like labels, are encoded in UTF-8. > > Does that mean,

Re: LSD0004 call for reviews

Thank you very much Maxime. I will look into the feedback this week. Just a side note: LSD0004 (the DHT) ist still in a very early, rough state. LSD0001 (GNS) is what is currently in the final stages and needs some fresh eyes before submission, if you are interested. :) Anyway. As soon as I

Re: printf-like output for gnunet-search

Hi! If there is a use case for this kind of functionality this lgtm. Altough, I do wonder what specifically triggered this. Is there anything wrong with the default output? BR Martin > On 5. Feb 2022, at 09:09, madmurphy wrote: > > Okay, after thinking about it I did not like that the

Re: Post-quantum secure hierachical deterministic key derivation

There is a (kind of) new paper which is shows how to do the blinding (we do not really need a full blown HDKD scheme) for current PQ signature schemes: https://eprint.iacr.org/2021/963.pdf They also have (C-based) implementations, which is nice. BR > On 23. Dec 2020, at 14:20, Jeff Burdges

Re: Issue re: the website (and others)

Hi, thanks for the report. When you go to https://bugs.gnunet.org/my_view_page.php on the top right next to your username you can select the project. The website is "gnunet-www". Ideally open an issue there, please. Regarding the messenger-gtk: We can create one if needed. Until then, filing it

Re: Next Mumble meeting

Hi Luis, I think we cancelled the meeting on 1.1. The next meeting will be on 2.2.2022 :) But, there will probably be an announcement before that. BR Martin > On 3. Jan 2022, at 03:30, Luis wrote: > > Hello > > When will be the next Mumble Meeting? Or did I miss the January one? > > []s, >

LSD0001: The GNU Name System update

Hi, we have recently as part of the IETF ISE review significantly revised the GNS specification [1]. In case any of you are interested or have too much time on their hands, reviews are very welcome :) Best Martin [1] https://lsd.gnunet.org/lsd0001 signature.asc Description: Message signed

Re: ReclaimID and MediaGoblin OpenID Plugin

Hi Tobias, the screenshot under [3] shows both a link for the reclaimID login as well as a manual entry. I am not sure if both can be used. My assumption is that the text entry is actually used in combination with OpenID Connect Discovery. OIDC Discovery uses Webfinger to discover the OpenID

Re: From gnunet-bcd to configure.ac

> On 22. Nov 2021, at 21:48, Alessio Vanni wrote: > > "Schanzenbach, Martin" writes: > >> 1. The uncrustify detection is now verbose. configure outputs the >> output of "uncrustify". Can we prevent that? It looks like an error. > > Y

Re: From gnunet-bcd to configure.ac

> On 22. Nov 2021, at 21:48, Alessio Vanni wrote: > > "Schanzenbach, Martin" writes: > >> 1. The uncrustify detection is now verbose. configure outputs the >> output of "uncrustify". Can we prevent that? It looks like an error. > > Y

Re: From gnunet-bcd to configure.ac

Thanks for the work! I reviewed the patch/branch and I am having two issues and two comments: 1. The uncrustify detection is now verbose. configure outputs the output of "uncrustify". Can we prevent that? It looks like an error. 2. Configure does not find my microhttpd anymore. I am not using a

Re: From gnunet-bcd to configure.ac

> On 21. Nov 2021, at 23:26, Christian Grothoff wrote: > > Dear Alessio, > > Wow, that read like a ton of great work was done that should be merged > 'soon' ;-). I have one comment: > > On 11/21/21 8:10 PM, Alessio Vanni wrote: >> - gnunet-namestore >> The '-u' option was broken. I forgot

Re: Remove me from the buildbot mailing list

The recent mail are probably due to the addition of nightly builds and the ARM worker. As those builds failed initially until setup correctly, all commit were considered the "culprits". But this should be ok now. What we could do is let buildbot only send reports to a mailing list instead of

Re: [PATCH] Improve bswap portability

> On 19. Sep 2021, at 19:41, Malte Voos wrote: > > Hi! > > Thanks for the explanation. This may be a stupid question, but why not > just use the bswap_* definitions from the libc? I do not know why it is/was done in this way, possibly because there are platforms that use gcc but not glibc.

Re: [PATCH] Improve bswap portability

Hi, thanks for noticing. bswap_* and the builtin __bswap_* are not the same. The former is a function sometimes provided by the libc, see gnulib [1]. The builtin is provided by compilers (maybe only gcc actually). I cannot find documentation, but it seems this is sometimes also called

Re: Pre-announcement of partial Scheme port of client libraries

Hi Maxime, > On 15. Sep 2021, at 12:57, Maxime Devos wrote: > > Hi, > > I've been porting parts of the client libraries of GNUnet to Guile (*) and > changing a few things. It now has sufficient functionality for a v0.1 > POC release (**), but I have a few questions to ask before I announce

Re: Gettext macros (and a couple other ones)

I don't think this is necessary for macOS, and keeping it would be questionable at best anyway ;) Removed in 279533005..3da9cbd62 > On 5. Sep 2021, at 19:01, Christian Grothoff wrote: > > Hi Alessio, > > I checked, and this was done (a long time ago) to support OS X builds. > There doesn't

Mantis git integration

Dear devs, you can now use git commit messages to reference mantis issues. In order to mention an issue, use "Issue #" anywhere in your commit message. Instead of "Issue", "Bug" and "Report" as well as plurals also work. If you want to automatically resolve the issue, use "Fixes #". An example

Re: Git server migration

> On 1. Sep 2021, at 19:55, madmurphy wrote: > > Any plans to install GitLab FOSS on the GNUnet git server (i.e., a fork of > GitLab with all proprietary code removed)? > > On Wed, Sep 1, 2021 at 6:21 PM Schanzenbach, Martin > wrote: > Hi, > > along with some

Git server migration

Hi, along with some other services, we are moving the gitolite service to another server. Unfortunately, we cannot move the gnunet.org domain just yet, so you may have to change your repository urls from g...@gnunet.org/repo to g...@git.gnunet.org/repo ( you need to add a "git." in front of

GNUnet 0.15.0 released

We are pleased to announce the release of GNUnet 0.15.0. This is a new major release. It breaks protocol compatibility with the 0.14.x versions. Please be aware that Git master is thus henceforth INCOMPATIBLE with the 0.14.x GNUnet network, and interactions between old and new peers will result

Re: gnunet-config and build informations (bug #5708)

IDK this does not sound like a good feature to me. I understand that it is possible, but it does not really make sense. Any application/project using gnunet(util) should provide its own *-config. Having gnunet-config be able to dynamically load different configurations is asking for trouble. I

Re: gnunet-config and build informations (bug #5708)

Hello Alessio, thanks for the work! I personally have never written an autoconf macro, but I would assume that it makes sense to have it. Regarding your patch: Lgtm, it addresses the first (basic) feature how I would expect it to happen. Which is allowing the caller to retrieve cflags or

Re: Compiling in OpenBSD: cannot find libsodium

Hi anoduck, I think we did not include --with-sodium switches. Can you try setting $ export CFLAGS="$CFLAGS -I/usr/local/include" and $ export LDFLAGS="$LDFLAGS -L/usr/local/lib" $ ./configure --prefix=... to see if that at least fixes your build? BR Martin > On 26. Jun 2021, at 04:25,

Re: CADET API: Obtaining the CADET channel closure?

Hi Alessio, > On 1. Jun 2021, at 21:23, Alessio Vanni wrote: > > Christian Grothoff writes: > >> Hi Alessio, >> >> You should store a copy of the 'cls' together with your channel handle. >> Typically, the 'cls' would actually point to the struct in which you >> store your channel handle. So

Re: Improving FCFS daemon

I am not sure of the NULL is a requirement of va_arg. The examples do not indicate that. And as I said the issue only arises when the argument is coming from gettext. So the issue lies somewhere else, but I do not know where. Maybe this is a general gettext/va_arg incompatibility. BR > On 16.

Re: Improving FCFS daemon

Ah nevermind. It is because your make_json checks for that. Looks good to me. The crash is fixed. Can be merged from my point of view. The only thing left is probably a link from the gns section on the homepage to the fcfs service. Thanks BR Martin > On 17. May 2021, at 13:36, Schanzenb

Re: Improving FCFS daemon

decide on a case-by-case > basis how high the bribe needs to be. ;-) Yes, we should draft that. BR Martin > > On 5/16/21 11:26 AM, Schanzenbach, Martin wrote: >> We may also think about if the FCFS service falls under the authority of >> GANA. >> Alessio made a

Re: Improving FCFS daemon

We may also think about if the FCFS service falls under the authority of GANA. Alessio made a good point wrt hidden names which would mean that we do not want to put all registered names in GANA anyway, but the handling of FCFS and its policy could be defined there. BR > On 16. May 2021, at

  1   2   3   4   >