intelmq
intelmq copied to clipboard
IntelMQ is a solution for IT security teams for collecting and processing security feeds using a message queuing protocol.
Going through and testing the documentation, I noticed that the unittest discover instructions assume that we have a global installation. If we follow the Developer guide, we might end up...
- [x] replace all links to old docs with the httpS://docs.intelmq.org/... link - [x] enforce HTTPS - [ ] monitor it? - [ ] (maybe) work on the CSS template...
The debian package, what is our main distribution format, patches IntelMQ source code to force LSB (/etc/intelmq) paths: https://github.com/certtools/intelmq/tree/develop/debian/patches It looks like we're also recommending those paths in our documentation....
On some occasions (after restarting Redis) connection to Redis is refused and this exception is raised: ``` File "/opt/venv/lib/python3.9/site-packages/intelmq/lib/pipeline.py", line 311, in count_queued_messages queue_dict[queue] = self.pipe.llen(queue) File "/opt/venv/lib/python3.9/site-packages/redis/commands/core.py", line 2668,...
Currently, scheduled bots has to be started outside IntelMQ, e.g. using cron. It would be good to introduce some scheduling directly in the IntelMQ, e.g. using https://pypi.org/project/APScheduler/ Two possible architectural...
https://github.com/certtools/intelmq/pull/2407/files has an interesting discussion on OS versions , what we officially support and what not. What would work (with maybe some tweaks or newer packages) but is not recommended...
Currently unmaintained Twitter collector bot is obsolete and presumably not work? * it uses unmaintained library [python-twitter](https://github.com/bear/python-twitter/) with recent issues claiming the authentication doesn't work [python-twitter/#721](https://github.com/bear/python-twitter/issues/721) * reason being Twitter...
Hello, From my IntelMQ instance running on Debian 12 (amd64) with IntelMQ 3.2.1, Cymru Whois bot expert failed with following error messages: ``` cymru-whois-expert: Loading destination pipeline and queues {'_default':...
Rationale: * [security] `stomp.py` in versions older than `4.1.12` always uses the old `ssl.wrap_socket()` API which has no support for server name indication (SNI) and hostname matching (newer versions of...
Currently, bots check their requirements only during startup. It would be helpful, if the `check()` method of bots does it as well, so we'll get the clear information when verifying...