Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixed spelling in SECURITY.md #489

Merged
merged 2 commits into from
Jul 28, 2018
Merged

Fixed spelling in SECURITY.md #489

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b86c1a8
Fixed spelling in SECURITY
pointydev Jul 1, 2018
429a313
fix(grammar) Fix spelling & comma splices in Security file
rumblefrog Jul 28, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions SECURITY.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 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).