Add option to NOT store key on server about end_to_end_encryption

[tobiasKaminsky]

Indeed we want to make this optional. So the user would have to enter a key file on setup of an already initialized account.
On initial setup then also the "publish private key" can be optional.

As this is possible without changing the metadata file, I think this can added without problems later.

We did it first this way as it is risky if you loose your private key and for most user the encrypted and uploaded private key is enough.

@LukasReschke please correct me if I am wrong on any point.

[schiessle]

I agree with @tobiasKaminsky. This is on the road map but will be probably a v2.0 feature.

[sunjam]

Pardon the silly question, but why is the server app currently needed when the work is being done on the client device?

[tobiasKaminsky]

Server app is

• handling encrypted private/public keys, otherwise user would have to transfer them from one device to another manually
• stores/updates encrypted metadata per folder

It is acting like a "stupid" file server, and does not have any real logic.

[jonathancross]

Is there work being done to allow use of keys on an a client-side hardware token (eg Yubikey)?

[sunjam]

Hardware token sounds like a good new issue to post if nothing comes up in search.

…

On Fri, Nov 6, 2020, 8:08 AM Jonathan Cross ***@***.***> wrote: Is there work being done to allow use of keys on an a client-side hardware token (eg Yubikey)? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#8 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AANUKZQAJEDUKLZG6XY7Y7DSOQNRRANCNFSM4D74BJHQ> .

[sunjam]

handling encrypted private/public keys, otherwise user would have to transfer them from one device to another manually

This is exactly what I would find preferable related to this issue: Only allow users to transfer & recover keys between devices manually (if they prefer it that way). Thank you all for working on this project! 👍