You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to search for attributes that do not have a set first_seen value (value set to None).
When using the PyMISP search functions as follows: pymisp.search(controller='attributes', first_seen=None)
The returned results are all attributes. If any integer value is supplied that's not a period such as '24h', then all the attributes WITH a first_seen value are returned.
Is there a way to search for attributes ONLY with a first_seen value of None? Can this be implemented if not available now? Also if possible, the args first_seen and last_seen should be added to the documentation under the search function as they do work.
The text was updated successfully, but these errors were encountered:
None is discarded on PyMISP side. I'm pretty sure MISP is also discarding searching for None, but I'll let one of my colleagues answer on that point (cc @iglocska@righel@mokaddem).
If that is implemented on MISP side, we need to come up with a generic approach for such search requests because they cannot be the default, and might end-up returning crazy amount of data.
@iglocska + @righel -- 2.4.196 ... Should we ddelete this off our wish list, i.e. support will not be forthcoming? Not mission ciritical, but we do have a use case for this. Thx.
I would like to search for attributes that do not have a set first_seen value (value set to None).
When using the PyMISP search functions as follows:
pymisp.search(controller='attributes', first_seen=None)
The returned results are all attributes. If any integer value is supplied that's not a period such as '24h', then all the attributes WITH a first_seen value are returned.
Is there a way to search for attributes ONLY with a first_seen value of None? Can this be implemented if not available now? Also if possible, the args first_seen and last_seen should be added to the documentation under the search function as they do work.
The text was updated successfully, but these errors were encountered: