MISP/misp-rfc

Clarify meaning of ID "human-readable identifier"

rooterkyberian opened this issue · 2 comments

id represents the human-readable identifier associated to the event for a specific MISP instance.

Currently https://github.com/MISP/MISP project uses integers for IDs, but if I'm reading this correctly this is just implementation specific and any other implementation could put here whatever they wanted (another UUID or slug name or some kind of hash).

Indeed, the RFC is based on the MISP core implementation. Where the practice is to have an integer represented as a string for the ID. @iglocska what do you think?

If that is the case please it would be good to add the number range constrains. I have read skimmed MISP software source code, but it seems the ID is limited by MySQL int(11) field, i.e. signed 4-byte integer. On PostgreSQL it seems to use twice the bytes for the ID, but MySQL is the default, right?