/waffle

Web Application Firewall, made in go.

Primary LanguageGoMIT LicenseMIT

WAFFLE

drawing

Documentation

This is github wiki's based documentation of the project:

Introduction

Probably you know about CloudFlare, every one knows, but this is a partially paid solution. As the open source community we are missing a real modular and open source Web Application Firewall that could be used in the place of CF.

How to run / Develop ?

Prerequisites

  • Go 1.22+
  • golangci-lint
  • make (if windows, try using chocolatey)
  • openssl (if windows, try using git bash)
  • mockery
  1. Create certificates and FS embed go file provider make certs_windows [//]: # (2. Execute docker compose up -d to create needed infrastructure)
  2. Set environment variables before running the proxy:

Generate certificates

Execute make certs_windows and go through process. It should certs in the .cert directory.

Planned features / Architecture

To bo honest, I'm learning how to write WAF from the scratch, so this part will be updated after a while.

  • XSS protection (HTML + we can take a look on sql injection)
  • DDOS protection

What I have learned?

  • Neovim
  • DDOS protection
  • XSS /SQLI protection

Contribution

What do I need to know to help?

If you are looking to help to with a code contribution our project uses GO, k8s.

How can I do that?

Never made an open source contribution before? Wondering how contributions work in the in our project? Here's a quick rundown!

Find an issue that you are interested in addressing or a feature that you would like to add.

Fork the repository associated with the issue to your local GitHub organization. This means that you will have a copy of the repository under your-GitHub-username/repository-name.

Clone the repository to your local machine using git clone.

Create a new branch for your fix using git checkout -b branch-name-here.

Make the appropriate changes for the issue you are trying to address or the feature that you want to add.

Use git add insert-paths-of-changed-files-here to add the file contents of the changed files to the "snapshot" git uses to manage the state of the project, also known as the index.

Use git commit -m "Insert a short message of the changes made here" to store the contents of the index with a descriptive message.

Push the changes to the remote repository using git push origin branch-name-here.

Submit a pull request to the upstream repository.

Title the pull request with a short description of the changes made and the issue or bug number associated with your change. For example, you can title an issue like so "Added more log outputting to resolve #4352".

In the description of the pull request, explain the changes that you made, any issues you think exist with the pull request you made, and any questions you have for the maintainer. It's OK if your pull request is not perfect (no pull request is), the reviewer will be able to help you fix any problems and improve it!

Wait for the pull request to be reviewed by a maintainer.

Make changes to the pull request if the reviewing maintainer recommends them.

Celebrate your success after your pull request is merged! 🚀

Where can I go for help? If you need help, you can ask questions on our Discord: https://discord.gg/33azuUWnm4

What does the Code of Conduct mean for me?

Our Code of Conduct means that you are responsible for treating everyone on the project with respect and courtesy regardless of their identity. If you are the victim of any inappropriate behavior or comments as described in our Code of Conduct, we are here for you and will do the best to ensure that the abuser is reprimanded appropriately, per our code.

HTML injection are attacks agains the HTML tokenization algorithm, examples: img.png Basically, we need to tokenize input and check attributes, tags against a set of rules

Links: