Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handle KeyTransport message correctly #33

Open
wants to merge 2 commits into
base: dev
Choose a base branch
from

Commits on Feb 11, 2021

  1. Handle KeyTransport message correctly

    omemo_message_export_encrypted() should not return early if only its
    payload is absent.
    
    omemo_message_prepare_encryption() should be able to accept an
    outgoing_message without body, which would become a template of a
    KeyTransport message.
    
    Signed-off-by: HardenedVault <[email protected]>
    root-hardenedvault committed Feb 11, 2021
    Configuration menu
    Copy the full SHA
    5136540 View commit details
    Browse the repository at this point in the history

Commits on Feb 12, 2021

  1. Add logic for <keys/> nodes and "kex" attribute

    According to:
    https://xmpp.org/extensions/xep-0384.html#message-structure-description
    
    Nodes for encrypted symmetric <key/> for a particular recipient should be nested
    in a <keys/> node with its "jid" attribute set to the recipient's bare JID, with
    an optional "kex" attribute for key exchange usage.
    
    Functions related to these above are modified accordingly.
    
    Signed-off-by: HardenedVault <[email protected]>
    root-hardenedvault committed Feb 12, 2021
    Configuration menu
    Copy the full SHA
    90ca270 View commit details
    Browse the repository at this point in the history