Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
briar
briar
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 700
    • Issues 700
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 9
    • Merge Requests 9
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • briar
  • briarbriar
  • Issues
  • #1182

Closed
Open
Opened Mar 08, 2018 by akwizgran@akwizgranOwner

Encrypt DB key with hardware-backed key when available

The database key is encrypted with a key derived from the user's password. This is vulnerable to brute force attacks; scrypt makes them more expensive but doesn't prevent them.

When a hardware key store is available, we could add another layer of security by encrypting the database key with a hardware-backed key as well as the password-derived key.

https://nelenkov.blogspot.co.uk/2013/08/credential-storage-enhancements-android-43.html

https://nelenkov.blogspot.co.uk/2015/06/keystore-redesign-in-android-m.html

https://developer.android.com/preview/features/security.html#hardware-security-module

https://developer.android.com/training/articles/keystore.html

Related to #257 (closed).

Edited May 17, 2019 by Torsten Grote
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: briar/briar#1182