What's new in MineMeld 0.9.30

[lmori]

Release Date: 2016-12-02

How to update: Updating MineMeld

Core

- log retention is now configurable via file

- fixed a bug preventing the removal of old trace files

API

- fixed a session leak

Docker

- fixed a problem with volumes. Backup your config before upgrading !

Nodes

- new Miner for O365, this Miner can automatically collect IPs and URLs of any O365 product. Useful to simplify your O365 config if you just want to catch them all.

- dagPusher now accepts API Keys in alternative to username/password (thanks @ksteves1) 

Prototypes

- new prototype for the "O365 any" Miner called office365.any

UI

- indicator types of prototypes are enforced during configuration. This basically means the UI tries to prevent mistakes like connecting Miner of domain indicators connected to IPv4 aggregators. You can always remove these constraints by switching to expert mode.

- new UI for prototype library showing more details per prototype (indicators, confidence, share level, devel status, ...). Example: you want to look for high confidence OSINT domain feeds ? Search for "OSINT high domain". (thanks @kevin_thys)

[ksteves1]

1 more: you can now use api_key in the minemeld.ft.dag.DagPusher device list, instead of api_username/api_password.

[KlausGroeger]

How is the API-Key configured in dag.pusher? Via WebUI one is only able to put in the user:passwd combo.

[lmori]

HI @KlausGroeger,

this is not possible via the WebUI yet, but you can define an attribute in the device list YAML file called api_key.