Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • hive hive
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 86
    • Issues 86
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 22
    • Merge requests 22
  • 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
  • hive
  • hivehive
  • Issues
  • #288

Closed
Open
Created May 03, 2022 by Gandalf@gandalfMaintainer

[cli_wallet] race condition while saving a wallet could potentially lead to data loss

use case scenario alice love to play with Hive via cli_wallet but also loves to have a lot of windows/consoles open

  1. starts cli_wallet instance[1]
  2. gets distracted curating content through web interface
  3. starts cli_wallet instance[2]
  4. cli_wallet instance[2]: set_password xxx, unlock xxx, import_key key1, import_key key2, closes wallet, goes for lunch
  5. gets back to pc looks at instance[1], closes wallet

so at step 4 wallet will save with two imported keys but at step 5 it will save empty wallet without keys

solution would be to use .lock file in order to make sure that the file won't be overwritten?

Assignee
Assign to
Time tracking