github-germ

The fix I've proposed for the server side object dedup worked for PyMISP 2.4.133 `add_event, update_event, add_object` without any changes to PyMISP, i.e. setting `MISPObject.breakOnDuplicate` was passed in the `POST`...

Hi @cvandeplas -- I work with @netmg. I'm new to Maltego -- your plugin is very cool! And thanks for being so responsive here! Being that these recent postings peeked...

@cvandeplas Thanks for the feedback. Don't have cycles to attack this now, but it's in the queue.

@chrisinmtown -- I tested your version of `__init__.py` with MISP 2.4.141, and it worked for me. I placed my custom expansion enrichment module script in `.../site-packages/mypkg/mymod.py` and started with `misp-modules...

A few ideas: 1. Add an arg to `MISPEvent.add_attribute` like `ignore_dup=True` to stop an error being thrown. 1. Would also be nice if there was a way to simply revise...

A PyMISP client ingests hourly into fixed events from a premium feed provider. These events can contain 500k+ attributes. Experience shows that having the client retrieve the full event with...

Our `don't ask, don't tell` use case is implemented with big performance improvement where: * `don't ask` -- the client does not retrieve the huge event from the server to...

Or another thought, offer a similar method as the Default Feed `Delta Merge` feature somehow for PyMISP ingestions -- not sure if this is done via PyMISP calls or perhaps...

Recap: Feature Request to add an argument, perhaps called `ignore_dup` to PyMISP `add_object` and `add_attribute` that will ignore duplicate attributes or objects and NOT log that as an error.

I discovered issues with the server side MISPObject deduplication within an Event and have a proposed fix. Please see `Proposed fix for deduplicating MISPObjects within an Event via breakOnDuplicate` in...