-
-
Notifications
You must be signed in to change notification settings - Fork 59
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
v1.6 #323
v1.6 #323
Conversation
Signed-off-by: Jan Kowalleck <jan.kowalleck@gmail.com>
Signed-off-by: Jan Kowalleck <jan.kowalleck@gmail.com>
Signed-off-by: Basil Hess <bhe@zurich.ibm.com>
Signed-off-by: Jan Kowalleck <jan.kowalleck@gmail.com>
Signed-off-by: Basil Hess <bhe@zurich.ibm.com>
Signed-off-by: Steve Springett <steve@springett.us>
This PR follows our CBOM WG call from Oct 12. It removes the `detectionContext` property from components and merges them with `componentEvidence`. The following properties are added to evidence: - `lineNumber` - `offset` - `symbol` - `additionalContext` The plan is to make a separate proposal/PR for `keyword` The PR also removes the extra fields for confidence levels since they are already covered by `componentEvidence`. Tagging @stevespringett @n1ckl0sk0rtge @mrutkows
This addresses the use case described in IBM/CBOM#31: - Expiry and life cycle of any relatedCryptoMaterial (e.g. keys, tokens, password) should be expressible. This is done by merging the "key" asset type and "relatedCryptoMaterial" to "relatedCryptoMaterial", which contains the needed properties.
goal: improve documentation by consolidating elements regarding "version". pure refactoring, no new functionality was added, nor removed, nor changed. - [x] consolidate `version` - [x] consolidate `range` - [x] rename `range` definition to `version-range` - [x] add more examples - [x] review rendered documentation
Signed-off-by: Jan Kowalleck <jan.kowalleck@gmail.com>
Signed-off-by: Jan Kowalleck <jan.kowalleck@gmail.com>
Signed-off-by: Basil Hess <bhe@zurich.ibm.com>
The new property 'parameterSetIdentifier' replaces 'variant' and contains information about the parameter set identifying an algorithm. This can be, for example, the key length (in AES), the digest length (in SHA2), or the hash algorithm used internally (in SLH-DSA / FIPS205). The "description" field contains some examples. This PR is motivated by IBM/CBOM#37 and intends to address its use case. Tagging @stevespringett, @n1ckl0sk0rtge, @mrutkows, @GeroDittmann
Signed-off-by: steve.springett <steve.springett@servicenow.com>
Signed-off-by: andreas hilti <andreas.hilti@bluewin.ch>
Move comment in `$comment` to description for increased visibility. Closes: #336
Signed-off-by: Basil Hess <bhe@zurich.ibm.com>
Reviews the description fields and addresses my TODOs.
Signed-off-by: Steve Springett <steve@springett.us>
Signed-off-by: Steve Springett <steve@springett.us>
Signed-off-by: Basil Hess <bhe@zurich.ibm.com>
Adds 'combiner' as enum entry in 'primitive'. Addresses the use case when combinations of (e.g.) classical crypto like RSA is used together with QSC like Dilithium. An entry of this primitive allows to express the combiner used. Adding dependencies to RSA/Dilithium then allows to express the algorithms used in the combiner. Note: "combiners" are also known as "hybrids", but this term can be ambiguous so I prefer the term combiner.
Signed-off-by: Steve Springett <steve@springett.us>
Signed-off-by: Steve Springett <steve@springett.us>
Signed-off-by: Steve Springett <steve@springett.us>
Signed-off-by: Steve Springett <steve@springett.us>
schema/bom-1.6.xsd
Outdated
<xs:annotation> | ||
<xs:documentation>A version range specified in Package URL Version Range syntax (vers) which is defined at https://github.com/package-url/purl-spec/VERSION-RANGE-SPEC.rst</xs:documentation> | ||
</xs:annotation> | ||
</xs:element> |
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.
Wrong place annotated.
@jkowalleck - Which leaves the entirety of |
@jkowalleck -
|
@jkowalleck See XSD here |
Signed-off-by: Steve Springett <steve@springett.us>
|
Signed-off-by: Steve Springett <steve@springett.us>
@madpah Not really an issue, but I did make this explicit in f5d959b |
Signed-off-by: Steve Springett <steve@springett.us>
|
Signed-off-by: Prabhu Subramanian <prabhu@appthreat.com>
Signed-off-by: Steve Springett <steve@springett.us>
Signed-off-by: Steve Springett <steve@springett.us>
Added
Fixed
This was already correct via ProtoBuff schema.
license
entities by XML schema (#288 via #292)This was already correct in JSON/ProtoBuff schema.
property
entities by JSON schema (#371 via #375)This was already correct in XML/ProtoBuff schema.
licenses
inMetadata
by ProtoBuff schema (#264 via #401)This was already correct in XML/JSON schema.
Changed
$schema
values by JSON schema (#402 via #403)versionRange
(via3e01ce6
)version
(via #417)Deprecated
author
was deprecated. (via #379)Use field
authors
or fieldmanufacturer
instead.manufacture
was deprecated. (#346 via #379)Use "Metadata"'s field
component
's fieldmanufacturer
instead./bom/metadata/component/manufacturer
$.metadata.component.manufacturer
Bom:metadata.component.manufacturer
Documentation
bom-ref
/refType
(#336 via #344)d92e58e
)Texts were a taken from the existing ones in XML/ProtoBuff schema.
licenses
(#273 via #378)Test data