Fix for SPDX validation failure due to invalid CPE strings #45
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
I've fixed an issue where an error occurs when generating SPDX SBOM for packages with '+' in their names, due to an invalid CPE string. Also, I've fixed to escape special characters other than +. As spdx-tools does not support percent encoding, I'm using backslash escape encoding instead. This patch fixes: - AlmaLinux#43
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.
I've fixed an issue where an error occurs when generating SPDX SBOM for packages with '+' in their names, due to an invalid CPE string.
Also, I've fixed to escape special characters other than +. As spdx-tools does not support percent encoding, I'm using backslash escape encoding instead.
Note:
For this instance, we have adopted the '' escape method.
There is also the '%' escape method, and looking at the specifications for cpe and uri, it seemed that using that method would be better.
However, since spdx-tools is designed to only interpret the '' escape method, I've conformed to that approach.
This patch fixes: