New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

STIX Cyber-observable Objects SHOULD use UUIDv5. It is not a MUST. #186

Open

rpiazza opened this issue Aug 16, 2021 · 1 comment

Contributor

rpiazza commented Aug 16, 2021

see oasis-open/cti-stix-generator#20

Contributor

chisholm commented Aug 19, 2021

I tried this and the validator did merely warn, it was not an error (without --strict). I saw, for example:

[!] Warning: windows-registry-key--8e7c5803-ab54-40f6-a028-db07391d9fc4:
    {103} Cyber Observable ID value windows-registry-key--8e7c5803-ab54-40f6-a028-db07391d9fc4 is not a valid UUIDv5 ID.

Is this what you saw? It seems to be working correctly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment