MISP / AIL contribution tentative

hackathon.lu
1

Initially I wanted to fix this bug I reported few month ago: https://github.com/ail-project/ail-framework/issues/232

Being on a different laptop (OpenSuse) & not working with MISP since then, I had to go through the docs again to deploy MISP/AIL/LACUS. It was painful, but it sprung discussion with other hackathon participants & circl staff:

  1. I couldn’t get misp-docker to deploy successfully on my machine with podman compose ; it works with docker compose though. Xavier tried to debug with me but it’s still unclear if the issue is from my local setup or not
  2. I, in fact, did not need to deploy MISP to solve that issue :slight_smile: It sprung a discussion with another hackathon participant highlighting our shared feeling about the MISP ecosystem: it is not easy to grasp which components are the most important / hard or soft dependence.
  3. Deploying the ail-framework locally was also very painful. Again, it triggered some discussions:
    1. I made a PR against the project touches up the README.md to clarify that only Ubuntu 24.04 is tested/supported: https://github.com/ail-project/ail-framework/pull/415
    2. We discussed the existence in the repo of files that are described as not maintained / very likely broken (here) and how, under the persona of “i am a user discovering AIL”, the existence of these files is more disruptive than useful. Under a persona willing to contribute, it doesn’t help that much either: if there is a will to have a docker-compose file to deploy AIL, I think it’d be better to have a Github issue to state it rather than dead (but discoverable!) code in the repo. I’ll attempt to PR a dev container: https://github.com/ail-project/ail-framework/pull/416
1 Like