-
Notifications
You must be signed in to change notification settings - Fork 4
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Simplify the format support radically to only "feed_specific"
For now we only need the feed_specific format and in this step only for the two feeds for which formats had already been defined in intelmq-mailgen. Making this very simple hopefully will make it easier to implement the more complex logic we actually need later on. This solves several defects: - The logic that selects the feed specific CSV format now actually works (fixes #20) - The CSV format for Sinkhole-HTTP-Drone is now the same as that for Botnet-Drone-Hadoop. The former was apparently never tested because it had a typo in one of the IntelMQ identifiers (destination.id instead of destination.ip) - The template is chosen by intelmq-mailgen now. With the way the contact DB currently works, this is the only way to get the right template. The template depends on the feed-name which the contact DB does not know anything about at the moment. This will have to change in some way, but for now we get something that should actually work. How the template name is constructed is described in README.md Other consequences: - There are no fallback formats anymore. It's not clear how to handle cases where no message can be generated because the format is unknown. We need a better way than what we get with this commit (mailgen produces an exception and the notification remains in the database as unsent) but simply sending a very generic mail as previously is probably not the right solution either. That solution was an ad-hoc fix/workaround for a defect in earlier versions. See #23
- Loading branch information
1 parent
23b07eb
commit a055bd5
Showing
2 changed files
with
57 additions
and
183 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters