MISP Package / FreeBSD Port

Tomasz CEDRO

unread,

Jun 20, 2016, 5:20:08 PM6/20/16

to MISP development

Hello,

I am working on FreeBSD Port for MISP. I have done step by step procedure to make dependencies and core installed. Still, there are too many steps to perform during pre/post installation to get the process smooth and automated..

Are there any plans or will to make MISP more package friendly?

Are there plans to make MISP easily configured in one place or with some kind of wizard?

Best regards :-)
Tomek

David André

unread,

Jun 21, 2016, 2:44:24 AM6/21/16

to Tomasz CEDRO, MISP development

There is a recent script to help auto-install on ubuntu 16.04:
https://github.com/MISP/MISP/issues/1270
And it should be integrated in the MISP install directory on github
after some changes.

Do you want to do something similar for FreeBSD?

Regards,
David

> --
> You received this message because you are subscribed to the Google Groups
> "MISP development" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to misp-devel+...@googlegroups.com.
> To post to this group, send email to misp-...@googlegroups.com.
> To view this discussion on the web, visit
> https://groups.google.com/d/msgid/misp-devel/0678e4fb-2293-4ddc-b1b1-d11d07160899%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

CeDeROM

unread,

Jun 21, 2016, 9:14:16 AM6/21/16

to David André, MISP development

On Tue, Jun 21, 2016 at 8:44 AM, David André <elh...@gmail.com> wrote:
> There is a recent script to help auto-install on ubuntu 16.04:
> https://github.com/MISP/MISP/issues/1270
> And it should be integrated in the MISP install directory on github
> after some changes.
> Do you want to do something similar for FreeBSD?

Hello David :-) Yes. FreeBSD Port is a Makefile based automation for
dependencies, build, and install in a standardized way. It is a part
of Port Tree of the FreeBSD OS. It will not be compatible with any
existing scripts for Linux. But I have the port almost done :-)

That automation would imply:
1. All dependencies calculation and install.
2. Software package fetch, extract, build and copy/install.
3. Example configuration files distribution/copy.
4. Post install configuration is possible by hand or a script wizard.
5. No other script may run not network communication takes place during step 2.

I can now see some python modules and dependencies needs to be
distributed as a separate packages/ports.

There could be an example configuration provided with the MISP
package, not to generate them by hand on install. Preferably a MISP
configuration could be placed in /usr/local/etc/MISP instead the
package or target location itself.

Any other thoughts on how to package MISP are welcome I am willing to
try them out :-)