Skip to content

Issues: oasis-tcs/csaf

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.

Sign up for GitHub

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

111 Open 295 Closed
111 Open 295 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Description of test 6.1.34 needs clarification documentation editorial mostly nits and consistency question
#840 opened Dec 8, 2024 by oxisto
@tschmidtb51
[Exclude from changes list] Changes from previous version collector csaf 2.1 csaf 2.1 work editorial mostly nits and consistency
#838 opened Dec 1, 2024 by sthagen
@sthagen
1
Need real examples of VEX based on actual products and known vulnerabilities, such as Log4J call_to_action a call to action has been send out user-question
#832 opened Nov 20, 2024 by rjb4standards
@tschmidtb51
9
Clarify csaf.data.security.domain.ltd in Requirement 10: DNS path csaf 2.1 csaf 2.1 work editorial mostly nits and consistency
#831 opened Nov 20, 2024 by sonnyvanlingen
@tschmidtb51
Clarification on why test case 6-1-31-12 in CSAF2.0 is supposed to be valid csaf 2.0 csaf 2.0 work csaf 2.1 csaf 2.1 work editor-revision already worked on in the editor revision editorial mostly nits and consistency
#825 opened Nov 9, 2024 by oxisto
1
@tschmidtb51
4
Provide patched documents of CSAF v2.0 including ERRATA 01 to fix docs.oasis-open.org bug documentation oasis_tc_process OASIS TC process action
#823 opened Nov 4, 2024 by sthagen
@sthagen
Store a canonical CWE database for CSAF in the TC repo question
#821 opened Nov 1, 2024 by oxisto
1
Provide an expected failure "code" or "message" in testcases.json csaf 2.0 csaf 2.0 work csaf 2.1 csaf 2.1 work test related to tests in this repo
#820 opened Oct 31, 2024 by oxisto
1
Ensure VEX minimum requirements with CSAF csaf 2.1 csaf 2.1 work
#818 opened Oct 30, 2024 by tschmidtb51
@tschmidtb51
Clearly state hardware/software separation in product_tree csaf 2.1 csaf 2.1 work motion_passed A motion has passed
#817 opened Oct 30, 2024 by tschmidtb51
@tschmidtb51
Add test data for 6.1.7: duplicate items csaf 2.0 csaf 2.0 work csaf 2.1 csaf 2.1 work test related to tests in this repo
#815 opened Oct 30, 2024 by tschmidtb51
Enforce format validation csaf 2.1 csaf 2.1 work enhancement
#813 opened Oct 25, 2024 by tschmidtb51
@sthagen @tschmidtb51
Add test: Consistent PIH csaf 2.1 csaf 2.1 work motion_passed A motion has passed
#812 opened Oct 25, 2024 by tschmidtb51
@tschmidtb51
2
Include support for SSVC csaf 2.1 csaf 2.1 work motion_passed A motion has passed
#803 opened Oct 23, 2024 by justmurphy
@tschmidtb51
6
Clarify requirement 19: ASCII vs. Binary signature csaf 2.1 csaf 2.1 work editor-revision already worked on in the editor revision editorial mostly nits and consistency
#797 opened Oct 17, 2024 by tschmidtb51
1
@sthagen @tschmidtb51
8
Add an optional reference OpenEoX artefact in CSAF csaf 2.x Maybe future tc-discussion-needed
#795 opened Oct 16, 2024 by sonnyvanlingen
2
Add an optional reference to MISP artefacts in Profile 2: Security Incident Response more_info_needed Additional information is required to proceed
#794 opened Oct 16, 2024 by sonnyvanlingen
3
Consider adding legal contextual information in Profile 2: Security Incident Response tc-discussion-needed
#793 opened Oct 16, 2024 by sonnyvanlingen
2
Add an optional element in Profile 2: Security Incident Response indicating if own offerings and systems are affected tc-discussion-needed
#792 opened Oct 16, 2024 by sonnyvanlingen
2
Clarify terminology of initial release of document version in 3.1.11.1 Version Type - Integer versioning csaf 2.1 csaf 2.1 work motion_passed A motion has passed
#791 opened Oct 16, 2024 by sonnyvanlingen
@tschmidtb51
4
Clarify the inclusion of open-source projects for the value vendor in 3.2.1.8.1 Document Property - Publisher - Category csaf 2.1 csaf 2.1 work editor-revision already worked on in the editor revision
#790 opened Oct 16, 2024 by sonnyvanlingen
1
@tschmidtb51
3
Check code blocks for correct syntax csaf 2.1 csaf 2.1 work editorial mostly nits and consistency
#787 opened Sep 25, 2024 by tschmidtb51
2
The field name 'release_date' is confusing, consider changing the name to 'public_date' tc-discussion-needed
#782 opened Sep 24, 2024 by zmanion
@tschmidtb51
8
Support for Multiple Notes, Products, and IDs csaf 2.1 csaf 2.1 work tc-discussion-needed
#780 opened Aug 28, 2024 by santosomar
@tschmidtb51
3
Support multiple purl identifiers in product_identification_helper csaf 2.1 csaf 2.1 work motion_passed A motion has passed
#774 opened Aug 26, 2024 by mprpic
1
@mprpic @tschmidtb51
8
ProTip! Adding no:label will show everything without a label.