From de3aac174e2c2e3c2d9e6a3743e29510529ab94c Mon Sep 17 00:00:00 2001 From: Jan-Piet Mens Date: Thu, 22 Sep 2016 14:49:07 +0200 Subject: [PATCH] mention _decrypted --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 550d24e..c8c5008 100644 --- a/README.md +++ b/README.md @@ -918,7 +918,7 @@ The user/device separator in the array's strings may be a slash (`/`), a dash (` If compiled with `WITH_ENCRYPT` support (this is the default in our packages), the Recorder will handle messages from OwnTracks [devices which support payload encryption](http://owntracks.org/booklet/features/encrypt/). Each user / device requires a secret key which is configured on the device and which must be configured on the Recorder host in order for the Recorder to be able to decrypt the payloads. -Upon successful decryption, the Recorder processes the original (device-transmitted) JSON and stores the result in plain (i.e. un-encrypted) form in the store. +Upon successful decryption, the Recorder processes the original (device-transmitted) JSON and stores the result in plain (i.e. un-encrypted) form in the store, adding a `"_decrypted":true` tag to the JSON. ## Tips and Tricks