From a073514c4699fd23ac113b8ace025d0c56c3012f Mon Sep 17 00:00:00 2001 From: Laurent Cozic Date: Wed, 13 Dec 2017 22:38:47 +0000 Subject: [PATCH] Update README_spec.md --- README_spec.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README_spec.md b/README_spec.md index b46e769ed..a127be45b 100644 --- a/README_spec.md +++ b/README_spec.md @@ -27,7 +27,7 @@ Data | ("Length" bytes) (ASCII) The master keys are used to encrypt and decrypt data. They can be generated from the Encryption Service, and are saved to the database. They are themselves encrypted via a user password. -These encrypted master keys are transmitted with the sync data so that they can be available to each clients. Each client will need to supply the user password to decrypt each keys. +These encrypted master keys are transmitted with the sync data so that they can be available to each client. Each client will need to supply the user password to decrypt each key. The application supports multiple master keys in order to handle cases where one offline client starts encrypting notes, then another offline client starts encrypting notes too, and later both sync. Both master keys will have to be decrypted separately with the user password. @@ -35,4 +35,4 @@ Only one master key can be active for encryption purposes. For decryption, the a ## Encryption Service -The applications make use of the EncryptionService class to handle encryption and decryption. Before it can be used, a least one master key must be loaded into it and marked as "active". \ No newline at end of file +The applications make use of the EncryptionService class to handle encryption and decryption. Before it can be used, a least one master key must be loaded into it and marked as "active".