Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • L libotr-ng
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • 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
  • libotr-ng
  • Issues
  • #125

Closed
Open
Created Jul 17, 2018 by Jurre van Bergen@DrWhaxOwner3 of 3 tasks completed3/3 tasks

Add fallback behavior when receiving a non-interactive auth message

Created by: juniorz

When a user receives a non-interactive auth message they must first use their latest non-expired profiles to verify the received message. If the verification fails they should fallback to their previous non-expired profiles.

This is because the non-interactive auth message has no profile IDs anymore.

Tasks:

  • Remove ID from prekey profile.
  • Remove both profile IDs from the non-interactive auth message.
  • Implement fallback behavior for both prekey and client profiles.
Assignee
Assign to
Time tracking