Skip to content

David Menendez

My feedback

1 result found

  1. 20 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    David Menendez commented  · 

    I agree that the re-encryption could have some risks, but I had assumed that during the conversion we would be working in a copy and only once all steps are successfully done, the original data would be removed.

    For me, these would be the key parts it should ensure:

    - Integrity of the data: this means that we need to work in "a copy" to allow the rollback if something goes wrong without loosing data.
    - Folder structure for messages and tags are kept as they are in the original encryption.

    I truly hope this gets implemented soon, otherwise we are using a service with a expire date depending on when you first logged in; of course, nowadays you can assume you lose data and can create new keys and forget about previous data, but this is currently a no-sense to me.

    David Menendez shared this idea  · 

Feedback and Knowledge Base