diff options
| -rw-r--r-- | docs/attachments.rst | 2 | ||||
| -rw-r--r-- | docs/incoming_box.rst | 279 |
2 files changed, 132 insertions, 149 deletions
diff --git a/docs/attachments.rst b/docs/attachments.rst index 7435eb4f..9561edcf 100644 --- a/docs/attachments.rst +++ b/docs/attachments.rst @@ -1,3 +1,5 @@ +.. _blobs-spec: + Document attachments ==================== diff --git a/docs/incoming_box.rst b/docs/incoming_box.rst index 4418887b..571830a2 100644 --- a/docs/incoming_box.rst +++ b/docs/incoming_box.rst @@ -1,18 +1,18 @@ -Soledad "Incoming Box" Functional Specification -=============================================== +Soledad "Incoming Box" Specification +==================================== -*A mechanism for writing encrypted data into a user database, to be processed and synced afterwards.* +*A mechanism for Trusted Applications to write encrypted data for a given user into the Soledad Server, which will sync it to the client to be processed afterwards.* -* **Version**: 0.1.0 -* **Date**: 8 jun 2017 -* **Authors**: kali, vshyba +* **Version**: 0.2.0 +* **Date**: 27 jun 2017 +* **Authors**: kali, drebs, vshyba .. contents:: :local: Overview -------- -The ``Incoming Box`` (or, in some contexts, ``incoming pools``) are a new feature of Soledad, beginning with release 0.9.7, that aim at improving the mechanism by which external trusted applications can write encrypted data into a specific user database, from where it will be further processed by the soledad client. +The ``Incoming Box`` is a new feature of Soledad, (from 0.10 forward), that aim at improving the mechanism by which external Trusted Applications can write data that will be delievered to a user's database in the server side, from where it will be further processed by the Soledad Client. This processing includes decrypting the payload, since the incoming data is expected to be encrypted by the Trusted Application. Design Goal ----------- @@ -21,8 +21,8 @@ The final solution should still be able to be the backend for different types of Features -------- -1. Deliver data (encrypted with a public-key mechanism) into a particular user's database in the server. -2. Provide a mechanism by which Soledad Client, acting on behalf of an user, can download the encrypted data, decrypt it, process it in any needed way, and eventually store it again in the conventional main storage that Soledad provides. +1. Deliver data (expected to be encrypted with a public-key mechanism) to the Soledad Server, so that it is written into the data space for a particular user. +2. Provide a mechanism by which Soledad Client, acting on behalf of an user, can download the data, process it in any needed way, and eventually store it again in the conventional main storage that Soledad provides. Since the data is expected to be encrypted by the delivery party, the client-side processing includes any decryption step if needed. 3. Allow to purge a document that has been correctly processed 4. Allow to mark a document that has failed to be decrypted, to avoid trying to decrypt it in every processing loop @@ -38,24 +38,27 @@ NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and Terminology ----------- -- ``Blob`` refers to an encrypted payload that is stored by soledad server as-is. It is assumed that the blob was end-to-end encrypted by an external component before being reaching the server. [link to Soledad BLOBS SPEC] +- ``Blob`` refers to an encrypted payload that is stored by soledad server as-is. It is assumed that the blob was end-to-end encrypted by an external component before reaching the server. (See the :ref:`Blobs Spec <blobs-spec>` for more detail) - A ``BlobBackend`` implementation is a particular backend setup by the Soledad Server that stores all the blobs that a given user owns. For now, only Filesystem Backend is provided. -- ``Incoming Box`` is a subset of the Blob storage space that provides semantics to store and process incoming message data chronologically. -- An ``Incoming Message`` makes reference to an abstract entity that matches exactly one message item, no matter how it is stored (ie, docs vs. blobs, single blob vs chunked, etc). It can represent one Email Message, one URL, an uploaded File, etc. +- An ``Incoming Message`` makes reference to the representation of an abstract entity that matches exactly one message item, no matter how it is stored (ie, docs vs. blobs, single blob vs chunked, etc). It can represent one Email Message, one URL, an uploaded File, etc. For the purpose of the email use case, an Incoming Message refers to the encrypted message that MX has delivered to the incoming endpoint, which is pgp-encrypted, and can have been further obfuscated. - By ``Message Processing`` we understand the sequence of downloading an incoming message, decrypting it, transform it in any needed way, and deleting the original incoming message. +- An ``Incoming Box`` is a subset of the Blobs stored for an user, together with the mechanisms that provide semantics to store, list, fetch and process incoming message data chronologically. Components ---------- * Soledad Server is the particular implementation that runs in the server (the twisted implementation is the only one to the moment). This exposes several - endpoints (document store, blob storage, incoming message box) that, for - simplicity, will be assumed to run under the same process space. -* The BlobsBackend is the particular implementation of the BlobsBackend + endpoints (documents synchronization, blob storage, incoming message box) + that. +* The BlobBackend is the particular implementation of the BlobBackend interface that the server has configured * Soledad Client is the particular client that runs in different desktop - replicas (the twisted implementation is the only one to the moment). It - executes a sync periodically, that syncs all metadata docs, and then downloads - the linked blobs on demand. + replicas in the u1db sense (the twisted implementation is the only one to the + moment). It executes a sync periodically, that syncs all metadata docs + (soledad l2db json documents), and then downloads the blobs on demand. The + blobs that need to be synced are both the encrypted blobs that are linked from + metadata docs, and in this case the blobs stored in the space for a given + Incoming Box. * BlobsManager is the component that orchestrates the uploads/downloads and storage in the client side. The client storage backend currently is SQLCipher, using the BLOB type. @@ -65,97 +68,75 @@ Components development of the Incoming Box. * On the client side, there's the client counterpart of the trusted application, that consumes the incoming messages. In the encrypted email case, this - component is the incoming service in Bitmask Mail. It is assumed, for - simplicity, that the consuming app shares the process memory space with the - soledad client, but this doesn't have to hold true in the future. + component is the Incoming Mail Service in Bitmask Mail. + The User Experience ------------------- -* For the end user, the behaviour of the Incoming Box in Soledad is completely - transparent. Periodically, new "messages" of any particular type will appear - on the Local Storage, without any other intervention that introducing the - master passphrase. -* From the application developer perspective, the "Incoming Box" will appear as - an iterable set that, in a given moment, will return all the messages that are - yet pending to be processed. The request can be qualified by some modifiers - (sorting, skipping, pagination). +* For the end user (ie, the user of Bitmask Mail in this case), the behaviour of the Incoming Box in Soledad is completely transparent. Periodically, new "messages" of any particular type will appear on the Client Trusted Application backed by the Soledad Client Storage, without any other intervention that introducing the master passphrase. + +* From the API perspective in the Soledad Client, the "Incoming Box" will appear an object that, upon executing one if its methods, will return an iterable set that, in a given moment, contains the UIDs for all the messages that are yet pending to be processed. The request can be qualified by some modifiers (sorting, skipping, pagination). This ``IncomingBox`` entity will be qualified by a particular namespace that defines a particular storage space inside an user store. Writing Data Into The Incoming Box ---------------------------------- -* Any payload MUST arrive already encrypted to the endpoint of the Incoming - Box. Soledad, at v1, will not add any encryption to the payloads. -* The knowledge to decrypt a given payload, at v1, is shared by both the Trusted - App that delivered the payload into the user Incoming Box (MX in this case), - and the domain-specific application that processes the incoming message on the - client side (incoming service in bitmask mail, in this case). +* Any payload MUST arrive already encrypted to the endpoint of the Incoming Box. + Soledad Server, at version 1 of this spec, will not add any encryption to the + payloads. +* The details of the encryption scheme used by the Trusted Application to encrypt the delivered payload (MX in this case) MUST be shared with the domain-specific application that processes the incoming message on the client side (Incoming Mail Service in Bitmask Mail, in this case). This means that the encryption schema MUST be communicated to the Incoming Box API in the moment of the delivery. * Incoming Boxes MUST NOT be writeable by any other user or any external applications. -Writing Data When User Quota is Exceeeded ------------------------------------------ -* The server SHOULD copy the payload to the permanent storage in the user database only after checking that the user current storage plus the payload size does not exceed the allowed quota, if any, plus a given tolerance limit. -* The Trusted Application SHOULD receive an error message as a response to its storage request, so that it can register the failure to store the date, or inform the sender in the case in which the trusted app is acting as a delegate to deliver a message. - Authentication -------------- -* The Trusted Application (MX) and the incoming box MUST share a secret, that is written into the configuration files of both services. +* The Trusted Application and the Soledad Server exposing the Incoming Box endpoint MUST share a secret, that is written into the configuration files of both services. * The Incoming Box MUST NOT be accessible as a public service from the outside. Listing All Incoming Messages ----------------------------- -* Soledad server will list all the messages in the Incoming Box every time that a client request it. +* Soledad server will list all the messages in the Incoming Box every time that a client requests it. * The server MUST return the number of pending messages. * The server SHOULD skip messages from the returned set beyond a given size limit, if the client requests it so. * The server MAY allow pagination. Processing Incoming Messages ----------------------------- -* The default state for a message in the Incoming Box is PENDING -* Before processing any message, a client MUST mark its blob as "PROCESSING", - reserving the message for itself so other replicas don't try to repeat - processing. -* Any replica MAY expire the PROCESSING flag if the defined - PROCESSING_THRESHOLD is passed, to avoid data left unusable by stalled clients. -* A message marked as PROCESSING MUST only be marked as PROCESSED by the replica - that marked it, which signals that is ready to be deleted. -* A Client MUST mark an incoming message as PROCESSED only when there are - guarantees that the incoming message has been processed without errors, and the - parts resulting of its processing are acknowleged to have been uploaded - successfully to the central replica. +* The Blobs containing the Incoming Messages need the capability to be + marked as in one of the following states: PENDING, PROCESSING, PROCESSED. +* The default state for a message in the Incoming Box is PENDING. +* Before delivering a Message to a client for processing, the server MUST mark the blob that contains it as PROCESSING, reserving the message for this client so other replicas don't try to repeat the processing. +* The server MAY expire the PROCESSING flag if the defined PROCESSING_THRESHOLD is passed, to avoid data left unusable by stalled clients. + * A message marked as PROCESSING MUST only be marked as PROCESSED by the server when it receives a confirmation by the replica that initiated the download request. This confirmation signals that the message is ready to be deleted. +* A Client MUST request to the server to mark an incoming message as PROCESSED only when there are guarantees that the incoming message has been processed without errors, and the parts resulting of its processing are acknowleged to have been uploaded successfully to the central replica in the server. Marking a Message as Failed --------------------------- -* A client SHOULD be able to mark a given message as temporarily failed. This - covers the case in which a given message failed to be decrypted by a - implementation-related reason (for instance: uncatched exceptions related to - encoding, wrong format in serialization). The rationale is that we don't want - to increase overhead by retrying decryption on every syncing loop, but we - don't want to discard a particular payload. Future versions of the client - might implement bugfixes or workarounds to try succesful -* Therefore, a client SHOULD be able to add its own version when it marks a - message as temporarily failed. +* A Soledad Client SHOULD be able to mark a given message as temporarily failed. This covers the case in which a given message failed to be decrypted by a implementation-related reason (for instance: uncatched exceptions related to encoding, wrong format in serialization). The rationale is that we don't want to increase overhead by retrying decryption on every syncing loop, but we don't want to discard a particular payload. Future versions of the client might implement bugfixes or workarounds to try succeed in the processing. +* Therefore, a Soledad Client SHOULD be able to add its own version when it marks a message as temporarily failed. * After some versions, a message should be able to be marked as permanently failed Deleting Incoming Messagges --------------------------- -* Any message in the ``Incoming Box`` marked as PROCESSED MAY be deleted by ANY client replica. -* Any message in the ``Incoming Box`` marked as PERMANENTLY FAILED MAY be deleted by ANY client replica. +* Any message in the ``Incoming Box`` marked as PROCESSED MAY be deleted by + the server. +* Any message in the ``Incoming Box`` marked as PERMANENTLY FAILED MAY be deleted by the server. + +Implementation Details +---------------------- -Implementation: Server Blob Backend ------------------------------------ +Server Blob Backend ++++++++++++++++++++ In the Server Side, the implementation of the ``Incoming Box`` MUST be done -exclusively at the level of the BlobStorage. The Blobs implementation in both -Soledad Server and Client have enough knowledge of the incoming box semantics to -allow its processing to be done without resorting to writing documents in the -main soledad json storage. +exclusively at the level of the BlobStorage. The Blobs implementation in both Soledad Server and Client have enough knowledge of the incoming box semantics to allow its processing to be done without resorting to writing documents in the main soledad json storage. + +For simplicity, the ``IncomingBox`` endpoint is assumed to be running under the same process space than the rest of the Soledad Server. Preffix Namespaces ~~~~~~~~~~~~~~~~~~ -The ``Incoming Box`` endpoint should reserve a uuid for any incoming blob, qualified +The ``Incoming Box`` endpoint should use an uuid for each incoming message, qualified by a reserved preffix per each Trusted App ('incoming-mx'). This is the main -mechanism to store the pool of "Incoming Messages" inside the bigger namespace +mechanism to store the set of "Incoming Messages" inside the bigger namespace of Blobs. This means that the general Blob spec MAY contemplate a mechanism to limiting @@ -166,99 +147,47 @@ LIST commands The server MUST reply to several LIST commands, qualified by namespace and by other query parameters. Some of these commands are optional, but the server -SHOULD reply to them signaling that they are not supported by the -implementation. +SHOULD reply to them signaling that they are not supported by the implementation. -LIST COUNT -++++++++++ -Returns the number of messages in the incoming box. If pending is True, only the subset marked as pending. +The Server MUST return a tuple with the UIDs of the messages. -Example:: - - list_count('incoming/mx', pending=True) - -LIST GET ALL -++++++++++++ -The response to a "get all" request by a client should return all the blobs under a given namespace. -It returns a list of uuids. +COUNT +~~~~~ +Returns the number of messages in the incoming box. By default, only messages marked as PENDING are returned. Example:: - list_get_all('incoming/mx') - - -LIST QUALIFIERS -+++++++++++++++ + IncomingBox.count('mx') -In order to improve performance and responsiveness, a list request MAY be -qualified by the following parameters that the server SHOULD satisfy. -The responses are, in any case, a list of the ``uuids`` of the Blobs. - -.. note: Should we extend this to other structure? Like a dict, containing - timestamps and sizes. - -- Pagination -- Skip by SIZE THRESHOLD -- Include messages with PROCESSING flag (replica uuid) - - -LIST PAGINATION -+++++++++++++++ - -* ``LIMIT``: number of messages to receive in a single response -* ``PAGE``: when used with limit, which page to return (limited by the number in LIMIT). (Note that, in reality, any client will just process the first page under a normal functioning mode). - -Example:: - - list_get_all('incoming/mx', limit=20, page=1) - -LIST SKIP-BY-SIZE -+++++++++++++++++ - -* SIZE_LIMIT: skips messages bigger than a given size limit, to avoid downloading payloads too big when client is interested in a quick list of incoming messages. +GET_ALL +~~~~~~~ +The response to a "get_all" request by a client should return all the blobs under a given namespace. +It returns a list of uuids. Example:: - list_get_all('incoming/mx', size_limit=10MB) + IncomingBox.get_all('mx') -LIST ORDER_BY -+++++++++++++ -Server CAN allow an order_by parameter in LIST commands. - -* Chronological order (by default, implicit, older first) -* Reverse Chronological order (newest first) - -Example:: - - list_get_all('incoming/mx', order_by='date') -Example:: +Client side Processing +++++++++++++++++++++++ - list_get_all('incoming/mx', order_by='date_reverse') - -Implementation: Client side processing --------------------------------------- +It is assumed, for simplicity, that the consuming app shares the process memory space with the soledad client, but this doesn't have to hold true in the future. * To begin a processing round, the client starts by asking a list of the pending messages. * To avoid potentially costly traversals, the client limits the query to the most recent N blobs flagged as PENDING. -* To avoid downloading very big attachments, client can limit the query on a first pass to all pending blobs smaller than X Kb. - -Example:: - - incoming_box('mx').get_all(limit=100, size_limit=100) - -* After getting the PENDING list, the client MUST start downloading the blobs according to the uuids returned. -* Download happens as chronological order, from the list. It can also happen concurrently or one by one, as configured. -* The client MUST provide a mechanism so that any trusted application (bitmask mail) can execute a callback for each downloaded message to be processed. -* Attention SHOULD be payed to the callbacks not blocking the main event loop of the client. +* To avoid downloading bulky messages in the incoming queue (for example, messages with very big attachments), the client MAY limit the query on a first pass to all pending blobs smaller than X Kb. +* After getting the list of Incoming Messages in the PENDING set, the client MUST start downloading the blobs according to the uuids returned. +* Download SHOULD happen in chronological order, from the list. Download may happen in several modalities: concurrently, or sequentially. +* The Soledad Client MUST provide a mechanism so that any clientside counterpart of the Trusted Application (ie: Bitmask Mail) can execute a callback for each downloaded message to be processed. +* In the reference implementation, since the callbacks that the client registers are executed in the common event loop of the Soledad Client process, attention SHOULD be payed to the callbacks not blocking the main event loop. Example 1, serial:: - for blob_id in pending_list: - blob = yield blob_manager.get(blob_id, incoming=True) # this will trigger a local save as well - yield blob_manager.remote_set_flags(blob_id, ['PENDING']) + for blob_id in IncomingBox('mx').get_all(): + blob = yield blob_manager.get(blob_id) # this will trigger a local save as well success = yield process(blob) if success: yield blob_manager.delete(blob_id) @@ -269,14 +198,13 @@ Example 1, serial:: Example 2, concurrent:: def callback(blob_id, blob): - yield blob_manager.remote_set_flags(blob_id, ['PENDING', self.replica_uuid]) success = yield process(blob) if success: yield blob_manager.delete(blob_id) else: yield blob_manager.set_flags(blob_id, ['FAILED']) - for blob_id in pending_list: - blob_manager.get(blob_id, incoming=True) + for blob_id in IncomingBox('mx).get_all(): + blob_manager.get(blob_id) d.addCallback(callback) deferreds.append(d) yield gatherResults(deferreds) @@ -291,3 +219,56 @@ Still subject to discussion, but some features that are desired for future itera * Internalizing public key infrastructure (using ECC). * ACLs to allow other users to push documents to an user Incoming Box. * Provide alternative implementations of the Incoming Box endopoint (for example, in Rust) + +Writing Data When User Quota is Exceeeded ++++++++++++++++++++++++++++++++++++++++++ +* The server SHOULD move the payload to the permanent storage in the user storage space only after checking that the size of the storage currently occupied by the user data, plus the payload size does not exceed the allowed quota, if any, plus a given tolerance limit. +* The Trusted Application SHOULD receive an error message as a response to its storage request, so that it can register the failure to store the data, or inform the sender in the case in which it is acting as a delegate to deliver a message. + + +LIST QUALIFIERS ++++++++++++++++ + +In order to improve performance and responsiveness, a list request MAY be +qualified by the following parameters that the server SHOULD satisfy. +The responses are, in any case, a list of the ``uuids`` of the Blobs. + +.. note: Should we extend this to other structure? Like a dict, containing + timestamps and sizes. + +- Pagination. +- Skip by SIZE THRESHOLD. +- Include messages with PROCESSING flag. + + +PAGINATION +~~~~~~~~~~ + + +* ``LIMIT``: number of messages to receive in a single response +* ``PAGE``: when used with limit, which page to return (limited by the number in LIMIT). (Note that, in reality, any client will just process the first page under a normal functioning mode). + +Example:: + + IncomingBox.get_all('mx', limit=20, page=1) + +SKIP-BY-SIZE +~~~~~~~~~~~~ + +* SIZE_LIMIT: skips messages bigger than a given size limit, to avoid downloading payloads too big when client is interested in a quick list of incoming messages. + +Example:: + + IncomingBox.get_all('mx', size_limit=10MB) + +ORDER_BY +~~~~~~~~ + +Server CAN allow an order_by parameter in LIST commands. + +* Chronological order (by default, implicit, older first) +* Reverse Chronological order (newest first) + +Example:: + + IncomingBox.get_all('mx', order_by='date') |