Add note about baselayer security and encryption options to security

considerations

Author: hlxid

docs/getting_started/security_considerations.md

@@ -9,21 +9,38 @@ The first part consist of our security claims and the second part describes how
 ## Security claims
 
 These claims all assume that you use a good strong password and take care of it properly.
+Also a secure base layer is assumed here. Security Bugs bugs in node.js/V8, your browser or your operating system are possible and can comprimise your private data in nodecg-io. Possible malware or e.g. keyloggers on your computer may also compromise this security model.
+
+1.  No service configuration is accessible to someone with only filesystem access.
 
-1.   No service configuration is accessible to someone with only filesystem access.
     -   A exception to this is a nodecg-io install with automatic login as the password is stored in plain text.
-2.   No bundle will be able to access your plain text password.
-3.   All loaded bundles may change nodecg-io settings like deleting instances
-4.   All loaded bundles may access all your configurations and passwords.
+
+2.  No bundle will be able to access your plain text password.
+3.  All loaded bundles may change nodecg-io settings like deleting instances
+4.  All loaded bundles may access all your configurations and passwords.
+
     -   It is highly recommended to only use bundles you trust!
-5.   Anyone intercepting network traffic between the NodeCG instance and browser with a logged in dashboard can access all configuration and passwords.
+
+5.  Anyone intercepting network traffic between the NodeCG instance and browser with a logged in dashboard can access all configuration and passwords.
+
     -   It is highly recommended to configure NodeCG to use HTTPS when using untrusted networks (e.g. the internet, open wifi if your NodeCG port is not firewalled)
 
 ## Implementation
 
-1.   The configuration is stored encrypted only in a NodeCG replicant. If someone reads the persistent value of the replicant from the filesystem the configuration cannot be read because it is encrypted using your chosen password.
-2.   When you enter your password inside the dashboard it is used to derive a encryption key using argon2id. Only this encryption key is ever transmitted and leaves the browser tab. Therefore other bundles can listen to the communication but it only contains the derived encryption key, not your plain text password.
-3.   Bundles can listen to the login message from the dashboard to get the encryption key. This can be used to send authenticate messages to the nodecg-io-core bundle to add/delete instances, change service instance assignments and do everything that is possible in the dashboard.
-4.   As mentionted in 3 all bundles can get the encryption key. The encrypted configuration is stored in a replicant which can be accessed by all bundles as well. Using these two any bundle could decrypt the configuration and have access to it.
-5.   Same as in 3, everyone intercepting network traffic can intercept the encryption key that gets send to the core using NodeCG messages. 
+1.  The configuration is stored encrypted only in a NodeCG replicant. If someone reads the persistent value of the replicant from the filesystem the configuration cannot be read because it is encrypted using your chosen password.
+
+    -   AES Options:
+        -   Bit length: 256 bits
+        -   AES block cipher mode: CBC
+        -   Padding scheme: PKCS7
+
+2.  When you enter your password inside the dashboard it is used to derive a encryption key using argon2id. Only this encryption key is ever transmitted and leaves the browser tab. Therefore other bundles can listen to the communication but it only contains the derived encryption key, not your plain text password.
+
+    -   Argon2id options:
+        -   Memory size: 37 MiB
+        -   Iteration count: 2
+        -   Parallelism: 1
 
+3.  Bundles can listen to the login message from the dashboard to get the encryption key. This can be used to send authenticate messages to the nodecg-io-core bundle to add/delete instances, change service instance assignments and do everything that is possible in the dashboard.
+4.  As mentionted in 3 all bundles can get the encryption key. The encrypted configuration is stored in a replicant which can be accessed by all bundles as well. Using these two any bundle could decrypt the configuration and have access to it.
+5.  Same as in 3, everyone intercepting network traffic can intercept the encryption key that gets send to the core using NodeCG messages.

docs/getting_started/use_replicants.md

@@ -9,7 +9,7 @@ TODO: explain for what replicants are useful
 
 Current list of services with replicant support:
 
-- StreamElements
+-   StreamElements
 
 (more services with replicants will hopefully be added in the future)
 
@@ -56,11 +56,11 @@ Here's an example for the StreamElements service (replace the name with the serv
 
         ...
 
-	streamElements?.onAvailable((client) => {
+    streamElements?.onAvailable((client) => {
             ...
-	    // Connect your replicant to this nodecg-io service instance.
-	    client.setupReplicant(streamElementsReplicant);
-	});
+        // Connect your replicant to this nodecg-io service instance.
+        client.setupReplicant(streamElementsReplicant);
+    });
     }
 
     ```
@@ -72,5 +72,3 @@ In case you want to use the created replicant in your bundles extension you alre
 You can access the NodeCG replicant as usual. Use `replicant.value` to get the current state and `replicant.on("change", (newValue, oldValue) => { /* .... */ })` to be informed when the value of the replicant changes.
 
 To figure out what properties are available on the object value you can either look at the corresponding sample bundle or use autocomplete in your editor if you're using TypeScript.
-
-