Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

apply_critical_fixes() in configure_misp.sh turns off actions plugin every time the misp-core container comes up #63

Closed
UFOSmuggler opened this issue May 20, 2024 · 4 comments · Fixed by #66
Assignees
Labels
documentation Improvements or additions to documentation enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed

Comments

@UFOSmuggler
Copy link
Contributor

https://github.com/MISP/misp-docker/blob/master/core/files/configure_misp.sh#L264

I suspect this is forced off so that if the Action_services_url is incorrect, MISP doesn't drop its lunch. However, it doesn't seem to cause an issue if set to something that doesn't exist.

Perhaps this isn't needed after all? Otherwise, every time the container comes up we have to edit the config again to turn it back on.

Is there some other reason for this I am not aware of?

@UFOSmuggler
Copy link
Contributor Author

also, i guess setting the enrichment hover stuff is also kinda annoying

@ostefano
Copy link
Collaborator

I am not against this in principle, but I believe this is also done because until misp-modules are loaded, those settings are not persisted / it is not reliable to set them.

@UFOSmuggler
Copy link
Contributor Author

Perhaps testing for their existence in the database and/or config.php file would be more reasonable than overwriting the users choice?

If they exist, do nothing, otherwise set to safe defaults?

@ostefano
Copy link
Collaborator

Yep, that would be a sensible choice. I wonder how all this is affected by MISP.system_setting_db. Anyway, I think we should just test removing the setting instructions and see what is the default value on a clean install, and document it (as long as there are no side-effects).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed
Projects
None yet
2 participants