-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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.
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
crypto/xform: migrate to SPDX identifier #15252
Conversation
xform.c is used by core crypto driver framework; we need find an alternative implementation. |
isn't this file from openbsd? |
YES, it is from |
so i suspect it's somehow misreported by FossID? |
@jerpelea We scanned the file xform.c with Black Duck Security and it showed that the license was BSD-3-Clause and no risk was reported. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you @jerpelea :-)
Looks like this will break stuff, and the component is BSD can be SPDX marked as BSD? :-)
it was pushed here to raise awareness |
thanks for double checking |
Most tools used for compliance and SBOM generation use SPDX identifiers This change brings us a step closer to an easy SBOM generation. NOTE The code was reported as GPL by FOSS ID and Xiaomi scanned the file xform.c with Black Duck Security and it showed that the license was BSD-3-Clause and no risk was reported. Since there is no clause on the license it was concluded as 0BSD Refference apache#15252 Signed-off-by: Alin Jerpelea <[email protected]>
Most tools used for compliance and SBOM generation use SPDX identifiers This change brings us a step closer to an easy SBOM generation. NOTE The code was reported as GPL by FOSS ID and Xiaomi scanned the file xform.c with Black Duck Security and it showed that the license was BSD-3-Clause and no risk was reported. Since there is no clause on the license it was concluded as 0BSD Refference apache#15252 Signed-off-by: Alin Jerpelea <[email protected]>
@cederom please review and unlock the PR |
@xiaoxiang781216 @yamt @fxysunshine Thanks for all your answers |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you @jerpelea !! :-)
Most tools used for compliance and SBOM generation use SPDX identifiers This change brings us a step closer to an easy SBOM generation. NOTE The code was reported as GPL by FOSS ID and Xiaomi scanned the file xform.c with Black Duck Security and it showed that the license was BSD-3-Clause and no risk was reported. Since there is no clause on the license it was concluded as 0BSD Refference apache#15252 Signed-off-by: Alin Jerpelea <[email protected]>
Most tools used for compliance and SBOM generation use SPDX identifiers This change brings us a step closer to an easy SBOM generation. NOTE The code was reported as GPL by FOSS ID and Xiaomi scanned the file xform.c with Black Duck Security and it showed that the license was BSD-3-Clause and no risk was reported. Since there is no clause on the license it was concluded as 0BSD Refference #15252 Signed-off-by: Alin Jerpelea <[email protected]>
Most tools used for compliance and SBOM generation use SPDX identifiers This change brings us a step closer to an easy SBOM generation. NOTE The code was reported as GPL by FOSS ID and Xiaomi scanned the file xform.c with Black Duck Security and it showed that the license was BSD-3-Clause and no risk was reported. Since there is no clause on the license it was concluded as 0BSD Refference apache#15252 Signed-off-by: Alin Jerpelea <[email protected]>
Summary
Most tools used for compliance and SBOM generation use SPDX identifiers
This change brings us a step closer to an easy SBOM generation.
Impact
LICENSE
Testing
CI