Closed davidonzo closed 6 years ago
Yes, it is caused by a change in MISPEvent. I'll fix it over there because it makes more sense.
That one should fix it: https://github.com/MISP/PyMISP/commit/749acd70b5ff00f2f74809b51cfb6db66b9543df
Can you check?
All things considered, your approach is better for this specific usecase. Merging.
If you want I'm able to test the using your latest PyMISP. Just let me know.
And thanks for the fix, of course.
It's all good, thank you :)
In the latest VM version availables (ccb3118940f9fcdf356126bed4370f3e7b5900a2) STIX import does not work. Maybe caused by a change in another library (from pymisp import mispevent).
The error reported