Skip to content
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

Date checking in changes.csv #451

Open
JanHoefelmeyer opened this issue Sep 4, 2023 · 0 comments · May be fixed by #609
Open

Date checking in changes.csv #451

JanHoefelmeyer opened this issue Sep 4, 2023 · 0 comments · May be fixed by #609

Comments

@JanHoefelmeyer
Copy link
Contributor

Requirement 13 states:

The file changes.csv MUST contain the filename as well as the value of /document/tracking/current_release_date for each CSAF document in the sub-directories without a heading; lines MUST be sorted by the current_release_date timestamp with the latest one first.

Currently, the only checks performed are whether the date is valid and whether the lines are sorted. However, there is no check being made on whether the date corresponds to the respective /document/tracking/current_release_date.

This allows for completely arbitrary dates to be entered as long as they conform to the syntax.

To recreate, create a changes.csv and add an entry, inputting a wrong date.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants