logos-messaging/specs
1
0
Fork 0
mirror of https://github.com/logos-messaging/specs.git synced 2026-05-25 22:39:28 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update standards/application/inbox.md

Browse Source 
Co-authored-by: Igor Sirotin <igor.sirotin.1012@gmail.com>
This commit is contained in:
Jazz Turner-Baggs 2026-05-19 13:42:28 -07:00 committed by GitHub
parent 1c4eb7d1ad
commit 601ecc9fa4
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
standards/application/inbox.md
View File

@ -102,7 +102,7 @@ How these are transferred is out of scope for this protocol.
## Recipient Key Identifier ## Recipient Key Identifier
When receiving a payload it is initially unclear which Recipients ephemeral key was used by the sender in the noise handshake. When receiving a payload it is initially unclear which Recipients ephemeral key was used by the sender in the noise handshake.
The Recipient sends their ephemeral key out of band, and there may exist many such keys. The recipient could exhaustively attempt decryption with it's available keys however this is potentially inefficient. Additionally in the case of decryption failure, its ambiguious whether the ephemeral keys was never valid or has expired/consumed. The Recipient sends their ephemeral key out of band, and there may exist many such keys. The recipient could exhaustively attempt decryption with its available keys however this is potentially inefficient. Additionally in the case of decryption failure, its ambiguious whether the ephemeral keys was never valid or has expired/consumed.
To make this efficient, the Sender includes a short identifier for the key. To make this efficient, the Sender includes a short identifier for the key.