Add GROUP destination support with symmetric key encryption#4
Open
kageedwards wants to merge 1 commit into
Open
Add GROUP destination support with symmetric key encryption#4kageedwards wants to merge 1 commit into
kageedwards wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This adds GROUP type destination support to enable symmetric-key-based group communication, matching the behavior of Python Reticulum's
RNS.Destination.GROUP.Changes
destination.js:
createKeys(),loadPrivateKey(key),getPrivateKey()for symmetric key management onGROUPdestinationsencrypt()anddecrypt()using Fernet, with error handling returningnullon decrypt failuresetPacketCallback(callback)for registering a receive handler, fired inonPacket()before the packet eventTesting
I've been building LXCF, an IRC-style semantic layer / protocol that runs seamlessly over LXMF, and needed group destinations for shared channel communication where multiple participants derive the same group destination hash and symmetric key from a shared passphrase.
I tested the group destination functionality with two LXCF Electron clients running on lxcf.js and rns.js, joining the same GROUP destination over TCP interfaces, exchanging messages bidirectionally.