diff --git a/docs/_static/recommended_workflow.png b/docs/_static/recommended_workflow.png new file mode 100644 index 000000000..bbab0bb34 Binary files /dev/null and b/docs/_static/recommended_workflow.png differ diff --git a/docs/administration.rst b/docs/administration.rst index a52d7753d..275883a2f 100644 --- a/docs/administration.rst +++ b/docs/administration.rst @@ -294,10 +294,14 @@ Documents can be stored in Paperless using GnuPG encryption. .. danger:: - Decryption is depreceated since paperless-ng 1.0 and doesn't really provide any + Decryption is depreceated since paperless-ng 0.9 and doesn't really provide any additional security, since you have to store the passphrase in a configuration - file on the same system as the encrypted documents for paperless to work. Also, - paperless provides transparent access to your encrypted documents. + file on the same system as the encrypted documents for paperless to work. + Furthermore, the entire text content of the documents is stored plain in the + database, even if your documents are encrypted. Filenames are not encrypted as + well. + + Also, the web server provides transparent access to your encrypted documents. Consider running paperless on an encrypted filesystem instead, which will then at least provide security against physical hardware theft. diff --git a/docs/changelog.rst b/docs/changelog.rst index 31bcdceed..8cdd7f49e 100644 --- a/docs/changelog.rst +++ b/docs/changelog.rst @@ -8,10 +8,8 @@ Changelog paperless-ng 0.9.0 ################## -* **Deprecated:** GnuPG. Don't use it. If you're still using it, be aware that it - offers no protection at all, since the passphrase is stored alongside with the - encrypted documents itself. This features will most likely be removed in future - versions. +* **Deprecated:** GnuPG. :ref:`See this note on the state of GnuPG in paperless-ng. ` + This features will most likely be removed in future versions. * **Added:** New frontend. Features: @@ -91,7 +89,7 @@ paperless-ng 0.9.0 * The presence of ``PAPERLESS_DBHOST`` now determines whether to use PostgreSQL or sqlite. * ``PAPERLESS_OCR_THREADS`` is gone and replaced with ``PAPERLESS_TASK_WORKERS`` and - ``PAPERLESS_THREADS_PER_WORKER``. See TODO for details. + ``PAPERLESS_THREADS_PER_WORKER``. Refer to the config example for details. * Many more small changes here and there. The usual stuff. diff --git a/docs/usage_overview.rst b/docs/usage_overview.rst index dd9213a86..a7820ab84 100644 --- a/docs/usage_overview.rst +++ b/docs/usage_overview.rst @@ -136,6 +136,7 @@ REST API You can also submit a document using the REST API, see :ref:`api-file_uploads` for details. + .. _usage-recommended_workflow: The recommended workflow @@ -147,6 +148,10 @@ is as follows. This workflow also takes into account that some documents have to be kept in physical form, but still ensures that you get all the advantages for these documents as well. +The following diagram shows how easy it is to manage your documents. + +.. image:: _static/recommended_workflow.png + Preparations in paperless =========================