Posts

Showing posts with the label gnunet

GNUnet Messenger API: May 2026

Image
Hi again, besides a few minor fixes in libgnunetchat that I missed before the last release of version 0.7.0 in March, I worked on the GTK4 interface of the Messenger application again. For example the decryption of files didn’t function properly since my last code abstraction in libgnunetchat and I noticed that while testing the file sharing in the GTK interface. I fixed multiple segmentation faults and synchronization issues inside the application that I noticed during testing and adjusting minor GUI components as well. Screenshot of the account creation dialog Big improvements are the following: The messages won’t take too much horizontal space anymore but try to fit as little space in the window as possible (this had to be ported from GTK3 to GTK4). The send and record button will allow short and long press interactions that enable a new context menu for sending delayed messages. The voice recording is much more consistent with toggling logic via button interaction and ...

GNUnet Messenger API: March 2026

Hello again, this month I’ve contributed a bit across all kinds of services from GNUnet . It started with minor adjustments to the Messenger service inside GNUnet, fixing an issue in the encryption of SECRET messages. Before that it would use an encrypt-and-mac paradigm that might lead to an attacker breaking the encryption. This has been changed to use the encrypt-then-mac paradigm which is more typical for authenticated encryption . I should note that these changes break compatibility to previous version of the service and it only improves the security attributes of the forward secrecy which is using the SECRET messages. There have also been adjustments to ensure compatibility with changes in the crypto module of GNUnet which introduced syntax changes. Adding to this I’ve started debugging GNUnet services from CORE , DHT , CADET to REGEX and more. I’ve noted that some services were using a completely different peer identity key than underlying communicators which handle the ...

GNUnet Messenger API: February 2026

Hello again, this month has been a bit different. Originally I thought to be done with my previous changes, ready for release but there were still some issues open in other services marked for the next release of GNUnet . So I waited at first for others to solve them until I asked myself whether I should take use of that time to integrate the newer PILS service functionality into the MESSENGER service . Then I started testing the current state of connectivity using TRANSPORT and CORE with the new PILS service and I noticed a few problems. So naturally I reported it, adding another issue to the list of things being solved before the next release. Sigh. Eventually I became too impatient deciding to at least go for fixing the new issue, I reported . Because it was stopping me from properly testing the MESSENGER service. That is how I ended up changing some parts around many different services to utilize the PILS service more consistently. The service supplies other services, client...

GNUnet Messenger API: January 2026

Hello there, the new year has started and I continued with my ongoing work back from November . The client-side library libgnunetchat has added a new function to generate a random secret which applications like messenger-gtk or messenger-cli can store using libsecret . Such a secret will be used to encrypt and decrypt locally stored keys for private messages in the Messenger service. In theory it’s also possible to replace the secret with a custom password selected by the user but I didn’t want to add a dialog for entering a password to the application because it adds an annoying additional step regarding usability. So the current implementation seems like a good compromise and it’s still possible to adjust it in the future. In case the secret gets dropped from the storage of libsecret by the user or the application would provide the wrong value by user input for example, only the previous keys can’t be decrypted and older messages stay inaccessible. New messages would use a newer...

Development in 2025

Hey everyone, welcome to the recap of my development from 2025. It has been another year and I put a lot of effort into improving the GNUnet Messenger again. As part of completing my study, I developed a concept for forward secrecy in distributed group contexts. Then I implemented and tested that concept within the GNUnet Messenger service. Also GNUnet made huge jumps in terms of progress over the year apart from the Messenger service as well. There are still open ends to reach “perfect forward secrecy” for example which I outlined in my master thesis but tackling those ends is planned. Additionally I started adding colors to the messenger-cli application using ncurses and the porting of messenger-gtk from GTK3 to GTK4 began. Most of these efforts could be completed next year. Other changes went into the GNUnet Messenger service to improve security against attackers gaining access to identity keys. With those changes private encrypted messages stay private but as mentioned in ...

GNUnet Messenger API: November 2025

Hey again, this month a few changes in GNUnet rolled out that would rename keys from its identity service to make clear they are blindable asymmetric keys. So I updated libgnunetchat to keep building against it. Additionally it was suggested that services like the messenger service in GNUnet should stop using those keys for HPKE (hybrid public key encryption) directly by deriving a keypair from the identity key. Instead it should use a separate key pair only for HPKE but signed by this blindable identity key. The advantage is pretty obvious. The least a keypair is reused for encryption purposes, the lower is the chance to reverse engineer the private key using samples of such encryption. The disadvantage is that such separate keys need to be stored additionally, exchanged between multiple devices by the receiver to decrypt private messages. So in simple terms: It makes everything a bit less efficient and more complex. But since I’d already implemented storing symmetric keys for ...

GNUnet Messenger API: October 2025

Image
Hi there, this month I started to port the messenger application from GTK3 and libhandy to GTK4 and libadwaita . So far the progress looks pretty good. I still need to adjust some widgets to avoid usage of some deprecated ones. There is some logic missing to upload files because file dialogs and widgets from GTK3 using those haven’t been ported exactly. So things need to change. Screenshot of the main window ported to GTK4 If you are interested in testing the changes so far, I have pushed all commits to a separate branch so far. While porting I have also noticed some bugs in the application and libgnunetchat API which might cause crashes or freezes. I will try to solve them before any release but I’m very confident that the next release will contain all the changes towards GTK4. Hopefully this will help long-term with reducing CPU load in case of image file previews and video streams. Also I’d like to add in-place video previews for shared files instead of relying on the vide...

GNUnet Messenger API: September 2025

Hey, a few days ago GNUnet 0.25.0 got released with the latest changes to the CORE layer and containing the new PILS service reducing the risk of being tracked while using GNUnet over a wider area. The MESSENGER service might still have some issues working properly with these changes but I will let you know here when I implemented necessary changes to utilize the new PILS service. This will be necessary because the MESSENGER service actually requires to track peers collaborating in message exchange to some degree. It won’t be necessary to link peer identities to individual chat room members. At the same time switching networks on abstract level like walking around with your mobile device or switching from physical connection to WiFi shouldn’t cause issues, message loss or heavy disconnections. So it will be fun to tackle this! However I’m very optimistic GNUnet is going in the right direction with all this work on its fundamental layers. There are still issues underlying in the TR...

GNUnet Messenger API: July 2025

Image
Hi there, unfortunately I didn’t make it to write a blog post last month. I was quite busy closing open ends of other projects while there were quite some bugs and issues to be solved in the Messenger service of GNUnet . On the bright side this means I have a lot to talk about this month. Most critical issues could be solved already, test cases of libgnunetchat pass again with all latest changes and the end-to-end encrypted chats seem to work as intended. I am still encountering some issues that messages do not get received immediately from chats or the chats can behave somewhat inconsistent. However it’s likely some condition caused by parallel events or a very specific order of events that’s difficult to reproduce. But these issues only seem to appear on reopening old chats from a previous session. The current sessions simply seem to work properly. Invitations do now respond to input feedback all the time and chat types get visualized depending on actual bits in a chat room’s key....

GNUnet Messenger API: May 2025

Hi again, to decrease complexity in the account system and key management I decided against separating identity keys from chat accounts and epoch keys for forward secrecy will instead be stored locally using GNS . The keys will be encrypted additionally using a key derived from the private identity key. So only the ownert of this key with storage access will be able to access those epoch and group keys to further access encrypted messages of certain epochs in the message graph. With those changes I could get rid of bigger API changes in the Messenger service . Key management is completely automatized now, once you provide a private key to the client API. So that makes further implementation a lot easier and it shouldn’t hurt confidentiality. As next step I want to improve the key exchange in regard to implement perfect forward secrecy. So that in case your long-term identity key gets into hands of an attacker, it’s still impossible to retrieve old epoch keys and access messages exch...

GNUnet Messenger API: March 2025

Hello again, since last month I tried to optimize the mechanism of forward secrecy further and indeed I was able to reduce the amount of messages required for a whole key exchange in a new epoch. So rather than scaling N scare if N is the amount of epoch members, it seems to scale linear now. That is quite an improvement but there’s still room for more adjustments. For example I realized recently that the current implementation is not providing perfect forward secrecy yet. That means if your long-term private key (the identity key to sign messages) gets compromised, an attacker might still be able to access messages from older epochs by request its keys from others. So to mitigate this, it will require changes that restrict requests of older epoch keys much more. Additionally deriving epoch keys via KDF could be adjusted to make it much more difficult to brute-force any epoch key from messages with HMAC using keys from the KDF. Once that’s done, there’s still work to do for allow...

GNUnet Messenger API: February 2025

Image
Hi again, My progress on the forward secrecy in the Messenger service of GNUnet is coming to a state where I have proper testing and results. You can find the current state of tests and benchmarks in a development branch of libgnunetchat which utilize a new ping tool for the Messenger service. The tool sends a TEXT message into a selected chat room and waits for other clients using the same tool but acting as receiver to send a TAG message back choosing the TEXT message as target. As a result the sender will measure and print out the delay between sending and receiving the response. Like that it’s possible to measure latency added via the implemented forward secrecy as well as its key exchange mechanism. The results so far are a mixed bag to be honest. Good news is that latency and general cost by symmetric encryption is negligible once the key for an epoch is exchanged. However bad news is that the amount of messages required for a proper key exchange as well as group formation...

GNUnet Messenger API: January 2025

Hello there, so I got some news for you again regarding my progress on the GNUnet Messenger service as well as the applications. Because there has been a GNUnet release last month which made libgnunetchat and the messenger applications using it incompatible, I needed to implement some changes, fixes and announced a new release . The forward secrecy I’m implementing in the Messenger service of GNUnet is still on development branch though. It will take some time until those changes are ready for release. But I got quite a bit of progress. The members of a chat actually start building groups, exchanging keys to form a tree structure as suggested in my last post from December . If any member of such a group is missing an epoch key, they will delay depending on their position inside their group the appeal for the missing key to then authorize the whole group after gaining access. This way ideally just one member will send an appeal, receive access, send an authorization and the rest of ...

Development in 2024

Hey everyone, welcome to my yearly recap of the year 2024. What happened? What did I work on? Well, quite a lot actually. So let’s start with the biggest project and continue from there. The GNUnet Messenger got funding from NLnet again as I mentioned in the end of last year. The new goal was to improve usability and add new features. What features are we talking about exactly? My concept was to achieve feature parity with most popular messaging apps but sticking to a decentralized context. For example I wanted to add profile pictures. But we can’t simply upload image files to a profile picture server/provider and poll from there for any new contact we get. So the solution required a bit of hacking around in the back-end. I used reclaimID from GNUnet to allow users sharing personal information with selected contacts of their choice and profile pictures may be such personal information for example. That means we can upload encrypted image files to a decentralized file sharing ser...

GNUnet Messenger API: December 2024

Hello, last month I’ve started to mention that I began to implement forward secrecy into the Messenger service of GNUnet . The fallback for key exchange in an epoch of messages is already working. Senders of messages will generate a new key just in time and announce it. Other members of that chat epoch will appeal the new key if missing and potentially gain access if allowed. As a way to improve key exchange further I’ve utilized a key derivation function to generate new epoch keys from ones of the previous epoch if and only if all members of the previous epoch are members of the new epoch (for example in case a new member has joined the chat). Otherwise a full exchange of a new and independent key is required to avoid access leakage to previous members that already left the chat. The last remaining step to improve efficiency further requires the setup of groups (or subgroups) inside an epoch. Those groups will either be formed by two members of an epoch or two groups of the same...

GNUnet Messenger API: November 2024

Hey again, It has been a few months since I last posted here since I finished my major project of the video and audio chat in the GNUnet Messenger application . I took a short break and now I’m working on a completely different part in the service again. So not a lot of visual progress but technical details to brag about. The plan is to finally implement proper forward secrecy into the Messenger service in GNUnet . So a theoretical attacker can not access or read messages posted prior to their event joining a group chat. This is ensured by encrypting the content of messages with a key that changes every time, a client joins or leaves a chat. Additionally because chains of events can diverge in the Messenger service a merge event of two message chains that use different keys will also cause a new key generation and exchange. The big problem I’m trying to solve is how to make this most efficient without relying or trusting a central entity. Because the whole service is designed from ...

GNUnet Messenger API: August 2024

Image
Hi again, as mentioned last time when talking about the user interface for discourses, I was looking into the implementation of video streaming this time. For this task I wasn’t really able to workaround using RTP or something comparable. So I tried looking into it again with success. The problem I had with it previously was actually related to me overlooking the structure GstRTPBuffer in the documentation of GStreamer . With that I was able to calculate the actual durations of each buffer. I could simplify the code handling video and audio streams into one with only some variables like datarate which differ. But overall it worked for RTP via both rtpL16pay and rtph264pay nodes. So I could transfer H.264 encoded video via GStreamer now without major issues. However one thing I needed to solve was getting encoding done on many different platforms and form factors. Because not every SoC or device offers hardware encoding and decoding which is preferable though reducing power cost ...

GNUnet Messenger API: July 2024

Image
Hi there, so this month I can show you the UI of the voice chat in current state. It might still not be perfect for all cases. But I think it’s a good compromise for desktop, mobile and overall consistency with other features. The discourse of any chat room can be opened as dialog above the main chat window to open and close a discourse. So this dialog will prevent texting to some degree. However it can be closed without leaving the discourse. So users can go back to chat texting and sending files, while being in active discourse over voice chat. picture of dialog open in front of chat messages It is possible to mute yourself via a button in the dialog. It is possible to adjust the overall volume of all audio. Also I have added some other buttons which are disabled for now for future functionality. All active members of a discourse are visually represented in the center grid of the dialog. All members of a chat room are visually listed in a sidebar. Maybe I will add some options ...

GNUnet Messenger API: June 2024

Hey, this month I’ve started working on the implementation of a voice chat feature. So far my local tests are looking good, transferring raw audio data from one client to another, essentially streaming it. Latency of all the cryptographic overhead does not seem to be an issue. It’s still possible there are optimizations needed but for a first implementation it’s looking good. I’m still waiting for further practical multi-device tests on either NAT traversal or improved peer perception in local networks using GNUnet . Also there’s still ongoing work on the testing system to create local multi-device test cases using network namespaces . Until one of those options is solid, it’s difficult to verify whether latency or bandwidth need further improvements. So I’ve continued implementing the required API in libgnunetchat and I’am already working on the graphical interface for it in the GTK client. Because those parts don’t need to wait for the back-end anyway and it makes practical tests...

GNUnet Messenger API: May 2024

Image
Hi again, there have been a lot of changes again this month. The issue (I mentioned last time ) in the reclaim subsystem from GNUnet was solved. So I adjusted libgnunetchat and the Messenger service regarding the changes in the API. Sharing attributes using tickets works properly and I implemented a way to share profile pictures through it. picture showing current contact info and views to deal with attributes The implementation works like this: You select an image file which gets published via FS subsystem in GNUnet. Then its URI to request and download the file from FS gets shared as attribute under a spcified name. If a user then decides to share that attribute with one of their contacts, they receive the URI and automatically download and display the profile picture as expected. picture showing the contact info for the current account to set a profile picture There’s still room for improvement. For example I might add a setting to automatically share a profile pi...