Self-Manage Devices - Githubissues

cryptomator / hub

Cryptomator Hub helps you manage vaults in large teams

GNU Affero General Public License v3.0

41 stars 9 forks source link

Self-Manage Devices #189

Closed overheadhunter closed 1 year ago

overheadhunter commented 1 year ago

Please agree to the following

[X] I have searched existing issues for duplicates
[X] I agree to follow this project's Code of Conduct

Summary

I want to manage my devices without the need of an vault owner to re-grant access

Motivation

As an unprivileged user I want to add and remove my own devices and instantly have access to vaults that I have been granted access to. I don't want to wait for the vault owner to rerun the "grant access" procedure.

Considered Alternatives

No response

Anything else?

No response

overheadhunter commented 1 year ago

Since we need to confirm the new device using some existing device, the workflow is started on a different device than it is finished on.

The hub acts as an information broker between those clients and we must protect the information from being tampered (e.g. an evil database admin exchanging the legitimate public key with one of his own). Therefore it is necessary for the new device to display some pairing code that is derived from its public key (e.g. its sha256). The existing device needs to prompt the user to enter this pairing code.

overheadhunter commented 1 year ago

Instead of using an existing device to confirm the new one (this is still possible to add in the future), we opted for a Setup Code in #207, which is a secret hold by the user that can be used to decrypt the user's private key.