Skip to content

Latest commit

 

History

History
13 lines (9 loc) · 839 Bytes

SECURITY.md

File metadata and controls

13 lines (9 loc) · 839 Bytes
Raw

Security

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 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, 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??

  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.