From b86c1a8f99df7f8f6c58e92dea3b815a4a3f5d63 Mon Sep 17 00:00:00 2001 From: Elliott Tallis Date: Mon, 2 Jul 2018 00:18:43 +0100 Subject: [PATCH 1/2] Fixed spelling in SECURITY --- SECURITY.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/SECURITY.md b/SECURITY.md index 4b2e88ca8..985359fc2 100644 --- a/SECURITY.md +++ b/SECURITY.md @@ -9,5 +9,5 @@ ## I Found a Security Hole, what do I do? -1. Open an issue on the GitHub repo, with all nessesary info. +1. Open an issue on the GitHub repo, with all necessary info. 2. If possible, open a Pull Request with a fix for the said Security Hole while following the instrucions in [CONTRIBUTING.md](https://github.com/sbpp/sourcebans-pp/blob/v1.x/CONTRIBUTING.md). From 429a313c67d8150a21dc2b4497e122dedc331f8c Mon Sep 17 00:00:00 2001 From: RumbleFrog Date: Fri, 27 Jul 2018 21:59:54 -0400 Subject: [PATCH 2/2] fix(grammar) Fix spelling & comma splices in Security file --- SECURITY.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/SECURITY.md b/SECURITY.md index 985359fc2..52355de90 100644 --- a/SECURITY.md +++ b/SECURITY.md @@ -3,11 +3,11 @@ ## Here are some steps to secure SourceBans++ 1. Use HTTPS! HTTPS is Key if you don't want MITM Attacks happening. Services such as Let's Encrypt provide free SSL Certificates. -2. Use a separate MySQL user just for SourceBans. Don't use the `root` MySQL user with SourceBans, make a seperate SQL account that only has access to the SourceBans DB. +2. Use a separate MySQL user just for SourceBans. Don't use the root MySQL user with SourceBans; make a separate SQL account that only has access to the SourceBans DB. 3. Make sure you do regular backups of your SourceBans Database. -4. Trust your Admins, don't give Admin access to your server(s) to a random stranger or a person you don't know. +4. Trust your admins, but don't give Admin access to your server(s) to a random stranger or a person you don't know. -## I Found a Security Hole, what do I do? +## I found a security hole. What do I do?? -1. Open an issue on the GitHub repo, with all necessary info. +1. Open an issue on the GitHub repo with all necessary info. 2. If possible, open a Pull Request with a fix for the said Security Hole while following the instrucions in [CONTRIBUTING.md](https://github.com/sbpp/sourcebans-pp/blob/v1.x/CONTRIBUTING.md).