3.2.4 Encrypt

Are you saving your notes on a Git service, a cloud or your hosting company ? Then it's a very (VERY!) bad idea to type sensitive informations in your notes...

Don't type, in plain text, password, FTP credentials, private information like your address, birthdate, ... in your file but encrypt them.

Encryption is really easy : just type your confidential info in a encrypt tag.

Here a fictive example : login and password for the demo site. The screen capture has been taken from the Typora editing tool.

The idea is thus : put between encrypt tag any sensitive informations.

Then, by displaying that note through the interface, every encrypt content will be processed and encrypted by using your password (see the settings.json encryption node)

The result will looks like :

The presence of the lock icon is an indicator that the displayed text is not stored anymore on the filesystem.

By opening back your note in a text editor, you'll see that any encrypt content has been encrypted.

The note is now safe.

Note : by editing the note through the Edit mode, just use the Encrypt button, it's easier. If your site is using a SSL certificate, the data is never stored or transmitted in plain text. By submitting the change, your browser is sending encrypted content (thanks to https), your webserver is receiving it, decrypt it and give it to the Marknotes script who immediatly encrypt it before saving the note on the disk. So, at no time, the sensitive information enclosed in encrypt tags is stored or transmitted in a non-secure way

But first, you'll need to mention your password : edit your settings.json file, locate the encryption node and type a value for the password variable. The password won't be asked again, you just need to put it there. If you're synchronizing your notes on a cloud, once again, don't store the settings.json file. Keep that file secret.