Uruk is a script for iptables firewall that simplifies packet filtering configurations, ideal for those seeking similar security settings.
If you are looking for an iptables firewall script that can handle similar packet filtering configurations across multiple machines, then Uruk might be the right fit for you. One of the unique features of this script is that it uses a template file for source addresses and network services.
To install Uruk, you need to run the `configure' shell script, which will attempt to guess the correct values for system-dependent variables that are used during compilation. Afterwards, it will create a `Makefile' in each directory of the package and one or more `.h' files containing system-dependent definitions. Additionally, it will create a shell script `config.status' that can be run in the future to recreate the current configuration and a file `config.log' that contains compiler output.
You can also use an optional file called `config.cache' to speed up reconfiguring. However, caching is disabled by default to prevent problems with accidental use of stale cache files. If you need to do unusual things to compile the package, you can try to figure out how `configure' could check whether to do them and mail diffs or instructions to the address given in the `README' so they can be considered for the next release.
If you are using the cache and at some point `config.cache' contains results you don't want to keep, you may remove or edit it. The file `configure.ac' (or `configure.in') is used to create `configure' by a program called `autoconf'. However, you only need `configure.ac' if you want to change it or regenerate `configure' using a newer version of `autoconf'.
In terms of updates, the most recent release of Uruk includes modified files such as `uruk/ChangeLog', `uruk/NEWS', `uruk/TODO', and `uruk/man/uruk-rc.azm.'
To install Uruk, you need to run the `configure' shell script, which will attempt to guess the correct values for system-dependent variables that are used during compilation. Afterwards, it will create a `Makefile' in each directory of the package and one or more `.h' files containing system-dependent definitions. Additionally, it will create a shell script `config.status' that can be run in the future to recreate the current configuration and a file `config.log' that contains compiler output.
You can also use an optional file called `config.cache' to speed up reconfiguring. However, caching is disabled by default to prevent problems with accidental use of stale cache files. If you need to do unusual things to compile the package, you can try to figure out how `configure' could check whether to do them and mail diffs or instructions to the address given in the `README' so they can be considered for the next release.
If you are using the cache and at some point `config.cache' contains results you don't want to keep, you may remove or edit it. The file `configure.ac' (or `configure.in') is used to create `configure' by a program called `autoconf'. However, you only need `configure.ac' if you want to change it or regenerate `configure' using a newer version of `autoconf'.
In terms of updates, the most recent release of Uruk includes modified files such as `uruk/ChangeLog', `uruk/NEWS', `uruk/TODO', and `uruk/man/uruk-rc.azm.'
What's New
Version 20051129: N/A