Ensure 'asn1' Field is Redacted in BSM Messages #46
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
Sync CDOT master with USDOT master
Sync CDOT develop with latest CDOT master commits
BSM "asn1" Field Redaction
Updated `Release_notes.md` for 2025 Q1 release
radishco
approved these changes
Jan 16, 2025
dan-du-car
reviewed
Jan 16, 2025
dan-du-car
approved these changes
Jan 16, 2025
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.
Problem
The newly added "asn1" field in BSM messages needs to be redacted to avoid potential unintended data exposure.
Solution
The code was updated to ensure the "asn1" field is redacted when processing BSM messages.
Testing
The updated image was tested with the ODE, and verification confirmed that filtered BSM messages no longer include the "asn1" field.