Support additional encodings (or even hashes?) for indicator matching #14
Labels
enhancement
New feature or request
good first issue
Good for newcomers
help wanted
Extra attention is needed
In #6, I'm implementing basic indicator matching with support for plain text, base64, and URL encoded text.
But with the framework we have, there's really no reason not to go beyond that. A few ideas for additional encodings we could support:
In addition, we could even compute common hashes of the indicators and check for those.
The text was updated successfully, but these errors were encountered: