Replace reg_value.type_id with official Microsoft Windows specification #865
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Use official Microsoft Windows Type ID for registry objects Reference: https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-rprn/25cce700-7fcf-4bb6-a2f3-0f6d08430a55 Reason: Avoid maintaining separate Type ID mapping for Microsoft Windows and another for OCSF registry value type ID specification Signed-off-by: alvinnieto <alvin_nieto@trendmicro.com>
floydtree
added
the
v2.0 and later
|
Agreed, no reason to maintain a separate registry. Just note that, this will be a breaking change and we'll need to consider it for v2.0 of the schema. |
floydtree
added
enhancement
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Use official Microsoft Windows registry "Type ID" for registry type id enum
Reference: https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-rprn/25cce700-7fcf-4bb6-a2f3-0f6d08430a55
Reason: Avoid maintaining separate registry Type ID mapping for Microsoft Windows and another for OCSF registry value type ID specification