Skip to content

Key revocation, expiration and management #7

@mbenlioglu

Description

@mbenlioglu

Problem

     Encryption/decryption keys that are used by client and server may expire or revoked any time! Currently the system does not explicitly handles such situations, and most likely won't work on its own, which will require manual manipulation of keys on both client & server sides in case of such a case.

Proposition

  • Add a key revocation scheme and overwrite expired/revoked keys with fresh ones. (Related to Old Keys are not overwritten #6 )
  • Check whether the keys in drive are updated, remove old key (don't just blatantly import what's there)
    • Need to be careful about security weaknesses here, make it clear what are we assuming
  • Actively request fresh keys from either side. (which will require a daemon to listen and respond such requests)

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingdesign issueProblems related to structure of the repohelp wantedExtra attention is needed

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions