smp protocol: short 1-time invitations and contact address links #1495
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
* smp protocol: short links types and other changes from RFC * add fields for queue link ID and data * create queue and ntf credentials with NEW command * all tests * simplfiy types, update rfc * update rfc * include SenderId in NEW request in case queue data is sent * store queue data and generate link ID if needed * update rfc * agent API and types * SMP commands and persistence for short links * SMP client functions for short links * agent client functions for short links * create rcv queue with short link (TODO secret_box) * encryption and encoding for link data, postgres client migration * test creating short link * get link and data, tests * comments * type signature
spaced4ndy
reviewed
Mar 27, 2025
spaced4ndy
reviewed
Mar 27, 2025
spaced4ndy
reviewed
Mar 27, 2025
spaced4ndy
reviewed
Mar 27, 2025
spaced4ndy
reviewed
Mar 27, 2025
…ecured (#1496) * agent: join connection when 1-time invitation short link is already secured * do not pass short link to join * delete short link record after connection
* agent: set/update and delete contact short link data * delete contact link data, tests * comments * type signature for GHC 8.10.7
epoberezkin
changed the title
…as for notifications (#1500)
* agent: binary protocol encoding for connection request * enable tests * test
* agent: types and encodings to use from the app * use action forks
…tests (#1505) * agent: padded encryption for link data, tests * lambda * test short links via proxy * tests: server persistence with short links * rfc: group links * shorten, restore, test short links encoding * rfc
* smp server: short links and owners for channels * types * support mutliple rcv keys * fix down migration, test/create server schema dump * reduce schema dump * parameterize type for link data by connection type * return full connection link data * test version * change short link encoding * test: print pg_dump output * server pages, link encoding * fix connection request when queue data and sender ID are created for old servers * test, change pattern * ci: install postgresql tools in runner (#1507) * ci: install postgresql tools in runner * ci: docker shell abort on error * fix pattern for ghc 8.10.7 * patch ConnReqUriData SMP encoding to preserve queue mode after decoding * test for RKEY * fix/test store log with RKEY --------- Co-authored-by: sh <[email protected]>
…andle preset server links (#1510) * smp server: .well-known folder for server pages for SimpleX apps to handle preset server links * add short link group path * test
…I for apps (#1511) * smp server: update server page for short links to correctly change URI for apps * change page titles
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
create notifications credential together with creating queuesmp protocol: remove creating notifications from NEW command, new ideas for notifications #1500.understand which IDs caused collision to retry if it's not client-supplied?communicate via subscription that 1-time invitation was read?