Skip to content

Commit 8f2eafc

Browse files
committed
add Tips section
1 parent 712fced commit 8f2eafc

1 file changed

Lines changed: 16 additions & 0 deletions

File tree

README.md

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -25,3 +25,19 @@ In this case it should be enough to just take the `sites-available/matomo.conf`,
2525

2626

2727
If you need to check the legacy nginx Matomo configuration, you can find it here: https://github.com/matomo-org/matomo-nginx/tree/1.0.99
28+
29+
## Tips
30+
31+
- never use Matomo without HTTPS
32+
- make sure you have configured Nginx to only accept modern and secure cryptography
33+
- check your website with https://www.ssllabs.com/ssltest/
34+
- compare your Nginx config with the "modern" template from https://mozilla.github.io/server-side-tls/ssl-config-generator/
35+
- this template is used by default in the `ssl.conf` file
36+
- decide if keeping outdated chiphers and TLS protocolls enabled to be able to track ancient browser is worth the risk of a downgrade attack for all your vistors (and admins)
37+
- never support SSLv3 and think about disabling TLSv1 and TLSv1.1
38+
- add `server_tokens off;` to your config to disable the `server: nginx` header on all requests and the nginx version on error pages
39+
- if you have enabled gzip compression (which improves performance greatly), be aware of the [BREACH](https://en.wikipedia.org/wiki/BREACH) vulnerability
40+
- think about enabling the [`Strict-Transport-Security`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Strict-Transport-Security) header, but keep in mind the implications
41+
- keep HTTP/2 enabled as it brings performance benifits with many small files (e.g. icons)
42+
43+
You know how to improve this config? Open a pull request or GitHub issue!

0 commit comments

Comments
 (0)