Skip to content

Releases: PietroCavaliere/Iptables-Best-Rules

v1.1.0 - Release Notes

29 Aug 17:09
d509e14
Compare
Choose a tag to compare

v1.1.0 - Changelog

This release builds upon the initial version of the iptables-rules.sh script by introducing critical functionality to check and install dependencies, ensuring the script operates reliably in various environments.

New Features:

  • Dependency Checking and Installation:

    • Added a function to verify and install required dependencies (iptables, xtables-addons-common) if they are not already present.
    • Automatically ensures that the iptables version is v1.8.7+ and xtables-addons-common is v3.19-1ubuntu1+, updating them if necessary.
  • Automatic Module Loading:

    • Integrated a mechanism to load essential xtables modules (xt_psd, xt_recent, xt_string) via modprobe, ensuring all necessary components are active.
  • User Experience Enhancements:

    • Simplified the script setup by automating dependency management and module loading, reducing the need for manual intervention.
  • Notes:

    • This update is backward-compatible with previous versions.
    • It's recommended to test the script in a controlled environment before deploying it in production.

Full Changelog: https://github.com/PietroCavaliere/Iptables-Best-Rules/commits/v1.1.0

v1.0.0 - Initial Release

29 Aug 08:31
d509e14
Compare
Choose a tag to compare

This release includes the initial version of the iptables-rules.sh script, which provides an optimal IPTables configuration aimed at mitigating various cyber attacks. The script includes custom rules designed to enhance security while maintaining system performance.

Key Features:

  • Comprehensive firewall rules for blocking common attacks.
  • Support for xtables modules such as xt_psd, xt_recent, and xt_string.
  • Easy customization for different environments.

Dependencies:

  • Iptables: v1.8.7+
  • xtables-addons-common: v3.19-1ubuntu1+

How to Use:

  1. Ensure dependencies are installed.
  2. Download and run the script with the necessary permissions.
  3. Customize the rules as needed for your environment.

Note:

This is the first stable release, and it is recommended to test the script in a staging environment before deploying it in production.