diff options
| author | Joel Hans <joel@netdata.cloud> | 2020-05-11 08:48:23 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-05-11 08:48:23 -0700 |
| commit | 74fda3de8e45e4211da8a574daabbfc30c74f0a9 (patch) | |
| tree | bcb5fb2a9ce32f759ca7bb139fb6e9da70e2126e /streaming | |
| parent | 9e8a0e173e2f4402fb081950b4b25d5fc0b62492 (diff) | |
Docs: Fix internal links and remove obsolete admonitions (#8946)
* Fixed a few more links
* Remove old syntax
* Abs-relative links to files in docs folder
* Trying to fix nother doc learn link
* Fix a few more links
* Add testing doc
* Tracking down mysteries
* Cleanup
* Update broken external links
* Remove index.html that appeared from testing
* Fix remainder of links
Diffstat (limited to 'streaming')
| -rw-r--r-- | streaming/README.md | 10 |
1 files changed, 6 insertions, 4 deletions
diff --git a/streaming/README.md b/streaming/README.md index dae41f257d..9ae5dacb5f 100644 --- a/streaming/README.md +++ b/streaming/README.md @@ -230,8 +230,10 @@ Netdata does not activate TLS encryption by default. To encrypt streaming connec The word `SSL` appended to the end of the destination tells the slave that connections must be encrypted. -??? info "Differences in TLS and SSL terminology" - While Netdata uses Transport Layer Security (TLS) 1.2 to encrypt communications rather than the obsolete SSL protocol, it's still common practice to refer to encrypted web connections as `SSL`. Many vendors, like Nginx and even Netdata itself, use `SSL` in configuration files, whereas documentation will always refer to encrypted communications as `TLS` or `TLS/SSL`. +> While Netdata uses Transport Layer Security (TLS) 1.2 to encrypt communications rather than the obsolete SSL protocol, +> it's still common practice to refer to encrypted web connections as `SSL`. Many vendors, like Nginx and even Netdata +> itself, use `SSL` in configuration files, whereas documentation will always refer to encrypted communications as `TLS` +> or `TLS/SSL`. #### Certificate verification @@ -276,8 +278,8 @@ Now you update the list of certificates running the following, again either as ` # update-ca-certificates ``` -!!! note - Some Linux distributions have different methods of updating the certificate list. For more details, please read this guide on [addding trusted root certificates](https://github.com/Busindre/How-to-Add-trusted-root-certificates). +> Some Linux distributions have different methods of updating the certificate list. For more details, please read this +> guide on [addding trusted root certificates](https://github.com/Busindre/How-to-Add-trusted-root-certificates). Once you update your certificate list, you can set the stream parameters for Netdata to trust the master certificate. Open `stream.conf` for editing and change the following lines: |