Update CHANGELOG and docs

CHANGELOG.md

@@ -1,4 +1,7 @@
-## 7.5.2 (unreleased)
+## 7.6.0 (unreleased)
+### New features
+- [PR #1055](https://github.com/rqlite/rqlite/pull/1055): Add new `join-read-only` permission.
+
 ### Implementation changes and bug fixes
 - [PR #1049](https://github.com/rqlite/rqlite/pull/1049): Ignore freshness when serving queries on Leader. Fixes [issue #1048](https://github.com/rqlite/rqlite/issues/1048). Thanks to @Tjstretchalot for the bug report.
 

DOC/SECURITY.md

@@ -60,17 +60,17 @@ An example configuration file is shown below.
   {
     "username": "mary",
     "password": "$2a$10$fKRHxrEuyDTP6tXIiDycr.nyC8Q7UMIfc31YMyXHDLgRDyhLK3VFS",
-    "perms": ["query", "backup"]
+    "perms": ["query", "backup", "join"]
   },
   {
     "username": "*",
-    "perms": ["status", "ready"]
+    "perms": ["status", "ready", "join-read-only"]
   }
 ]
 ```
 This configuration file sets authentication for three usernames, _bob_, _mary_, and `*`. It sets a password for the first two.
 
-This configuration also sets permissions for all usernames. _bob_ has permission to perform all operations, but _mary_ can only query the cluster, as well as backup the cluster. `*` is a special username, which indicates that all users -- even anonymous users (requests without any BasicAuth information) -- have permission to check the cluster and readiness. This can be useful if you wish to leave certain operations open to all accesses.
+This configuration also sets permissions for all usernames. _bob_ has permission to perform all operations, but _mary_ can only query the cluster, as well as backup and join the cluster. `*` is a special username, which indicates that all users -- even anonymous users (requests without any BasicAuth information) -- have permission to check the cluster status and readiness. All users can also join as a read-only node. This can be useful if you wish to leave certain operations open to all accesses.
 
 ## Secure cluster example
 Starting a node with HTTPS enabled, node-to-node encryption, and with the above configuration file. It is assumed the HTTPS X.509 certificate and key are at the paths `server.crt` and `key.pem` respectively, and the node-to-node certificate and key are at `node.crt` and `node-key.pem`