Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • briar briar
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 788
    • Issues 788
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 6
    • Merge requests 6
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • briar
  • briarbriar
  • Issues
  • #630

Closed
Open
Created Aug 31, 2016 by Torsten Grote@groteOwner

Introduction Protocol does not abort once in FINISHED state

While writing introduction protocol attacks for #627 (closed) I noticed that introducees do not handle ABORT messages once they are in the FINISHED state.

This can lead to a situation where the protocol is aborted by Bob due to an invalid MAC, but Alice has not only added Bob already, but also notified the UI of the successful addition of Bob. Do we also forcefully remove a contact that has already been added and activated? If so, do we need to introduce a new event to inform the user about that.

Assignee
Assign to
Time tracking