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

Don't read and modify config files directly #75

Open
ondj opened this issue May 11, 2016 · 2 comments
Open

Don't read and modify config files directly #75

ondj opened this issue May 11, 2016 · 2 comments

Comments

@ondj
Copy link

ondj commented May 11, 2016

Currently, IntelMQ manager reads and modifies config files directly by PHP script. But when location or format will be changed, it is necessary to change manager also.

My proposal is, that every interaction with IntelMQ should by done thought intelmqctr command. But this change requires updating this command to support configuration read and change.

@sebix
Copy link
Member

sebix commented May 11, 2016

I support this idea. As I focus on other things, there haven't been proposals yet (and the -manager should run in trusted environments only anyway).

My proposal is, that every interaction with IntelMQ should by done thought intelmqctr command. But this change requires updating this command to support configuration read and change.

Is intelmqctr a typo or a proposal for a new binary? Do you have ideas what scope the atomic commands could have? (e.g. one command to set a single option for a bot, or one command to set all options for a bot etc.)?

@aaronkaplan
Copy link
Member

aaronkaplan commented May 11, 2016

sounds good. @ondj do you have a proposal how this should look like?

@sebix sebix modified the milestones: Release 1.1, Future Sep 15, 2016
@ghost ghost added the help wanted label Jun 2, 2017
@ghost ghost added the backend label Aug 10, 2017
@ghost ghost modified the milestones: 2.0, 2.1.0 May 22, 2019
@ghost ghost modified the milestones: 2.1.0, 2.2.0 Feb 18, 2020
@ghost ghost removed this from the 2.2.0 milestone Jun 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants