MISP / MISP/misp-warninglists

Confusion about updating MISP after generating new warninglist list.json files

Open
#255 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
650
Forks
195
Avg merge
18h 17m
Merged PRs (30d)
74

Description

Maybe we've been doing it all wrong, but we have been running the tools/generate-crl-ip-domains.py script periodically in order to keep our warninglist updated.

Today, I went to update MISP via the web UI and hit this error while it was updating the submodule for misp-warninglists.

error: Your local changes to the following files would be overwritten by checkout:
	lists/crl-hostname/list.json
	lists/crl-ip/list.json
Please commit your changes or stash them before you switch branches.
Aborting
Unable to checkout '99c64074101b3b3a18727564350070895a4e0216' in submodule path 'app/files/warninglists'

The web UI seems to read from these git-managed files when it updates the warninglists, so I assume we are meant to update at this location:

 /var/www/MISP/app/files/warninglists/lists/crl-ip/list.json

But if we update there, how are we meant to clean up so that we can do MISP updates?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with tools/generate-crl-ip-domains.py and the web UI's app/files/warninglists submodule, including lists/crl-ip/list.json and lists/crl-hostname/list.json. Determine the supported workflow for regenerating these files, committing or reverting local changes, and updating the submodule; done means the process is documented without blocking future MISP updates.

Written by the indexing model from the issue text.

Assessment

Tech stack
git, python
Domain
devops, tooling
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.