Download the PHP package agenter-labs/laravel-firewall without Composer
On this page you can find all versions of the php package agenter-labs/laravel-firewall. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package laravel-firewall
Web Application Firewall (WAF) package for Laravel
This package intends to protect your Laravel app from different type of attacks such as XSS, SQLi, RFI, LFI, User Agent, and a lot more. It will also block repeated attacks and send notification via email and/or slack when attack is detected. Furthermore, it will log failed logins and block the IP after a number of attempts.
Note: Some middleware classes (i.e. Xss) are empty as the Middleware abstract class that they extend does all of the job, dynamically. In short, they all works ;)
Getting Started
1. Install
Run the following command:
2. Register (for Laravel < 5.5)
Register the service provider in config/app.php
3. Publish
Publish configuration, language, and migrations
4. Database
Create db tables
5. Configure
You can change the firewall settings of your app from config/firewall.php file
Usage
Middlewares are already defined so should just add them to routes. The firewall.all middleware applies all the middlewares available in the all_middleware array of config file.
You can apply each middleware per route. For example, you can allow only whitelisted IPs to access admin:
Or you can get notified when anyone NOT in whitelist access admin, by adding it to the inspections config:
Available middlewares applicable to routes:
You may also define routes for each middleware in config/firewall.php and apply that middleware or firewall.all at the top of all routes.
Notifications
Firewall will send a notification as soon as an attack has been detected. Emails entered in notifications.email.to config must be valid Laravel users in order to send notifications. Check out the Notifications documentation of Laravel for further information.
Changelog
Please see Releases for more information what has changed recently.
Contributing
Pull requests are more than welcome. You must follow the PSR coding standards.
Security
If you discover any security related issues, please email [email protected] instead of using the issue tracker.
Credits
- Denis Duliçi
- All Contributors
License
The MIT License (MIT). Please see LICENSE for more information.
All versions of laravel-firewall with dependencies
laravel/framework Version ^9.0
guzzlehttp/guzzle Version ^7.0
jenssegers/agent Version 2.6.*