Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • O otrv4
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1
    • Issues 1
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • OTRv4
  • otrv4
  • Issues
  • #195

Closed
Open
Created Jan 11, 2019 by Jurre van Bergen@DrWhaxOwner

Should we store the chain key of previous session?

Created by: claucece

This can happen:

  1. Alice sends an Identity message
  2. Bob answers with an Auth-R message
  3. Alice sends a Non-Int-Auth (after requesting prekeys), and goes to ENCRYPTED state
  4. Bob receives it and goes to ENCRYPTED state. Sends a data message
  5. Alice sends another identity message (in ENCRYPTED STATE)
  6. Bob should be able to receive it and start a DAKE again
  7. Bob will receive a data message from a previous session

For this, we can store the chain key chain_key_receiving[i][k], so the data message might be decrypted. This chain key should be in memory only for a short amount of time.

Assignee
Assign to
Time tracking