Rule Downloader
This is a tool to aid in the downloading and archival of Snort rulesets. It also includes a tool, rulechanges.py to itemize the changes from one version of a ruleset to another.
Configuration
The ruledownloader is configured with an INI style file. The configuration file is passed to the ruledownloader with the -c command line switch. Alternatively, the ruledownloader will look for a file named ruledownloader.conf in the current directory and use that.
Example Configuration
[general]
# The dest-dir parameter tells ruledownloader where to place the
# files it downloads. Subdirectories will be created under this
# directory for each conifgured ruleset.
dest-dir = .
# A ruleset configuration for a VRT subscription ruleset for Snort
# 2.9.0.4.
[ruleset vrt-subscription-2904]
# Set to no to skip downloading this ruleset.
enabled = yes
# The URL this ruleset is found at.
url = http://www.snort.org/sub-rules/snortrules-snapshot-2904.tar.gz/<yourOinkCodeHere>
# Another ruleset configuration.
[ruleset et-open-290]
enabled = yes
url = http://rules.emergingthreats.net/open/snort-2.9.0/emerging.rules.tar.gz
Directory Structure
Within the configured destination directory each policy will get its own directory based on on the name of the policy. That directory will contained timestamped directory names based on when the ruleset was downloaded. A symlink names 'latest' will point to the most recently downloader version of the ruleset.
Example
Given the et-open-290 ruleset configuration above the following directory structure will be created.
./et-open-290/201104070917/emerging.rules.tar.gz
./et-open-290/201104071531/emerging.rules.tar.gz
./et-open-209/latest -> 201104070917
Reporting Changes
The rulechanges script can report the difference between an old and new version of a ruleset.
Usage:
./rulechanges.py <oldRuleset.tar.gz> <newRuleset.tar.gz>
Metadata
Release files for ruledownloader 1.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| ruledownloader-1.0.0.tar.gz | 7.8 kB | Without provenance | Details for ruledownloader-1.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ruledownloader-1.0.0-py3-none-any.whl | Python 3 | none | any | Details for ruledownloader-1.0.0-py3-none-any.whl |
Total release size: 16.7 kB
Release files / ruledownloader-1.0.0.tar.gz
| Download URL | ruledownloader-1.0.0.tar.gz |
|---|---|
| Size | 7.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
607916b1b017493241653b65a77d169e1881b1cc58cc4cbc4e48d6f10971f44c
|
|
BLAKE2b-256 checksum How to use checksums |
c403d1cff4fe1b4a87d4af950cc23101d4934cd417437699f058c1add5b9b5b0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.16
|
Release files / ruledownloader-1.0.0-py3-none-any.whl
| Download URL | ruledownloader-1.0.0-py3-none-any.whl |
|---|---|
| Size | 8.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
08aae2e3c3da6647b012021aaa02bfbbca59319296564c4a4394a287055e4530
|
|
BLAKE2b-256 checksum How to use checksums |
b7cef327ea8a375394eb87e56ae3c1b0cab41ab792f19ca009094280da7278a7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.16
|
Security for ruledownloader 1.0.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.