Bump OVAL_SUPPORTED to 5.11.3 - #2259
Conversation
|
We should actually bump it to 5.11.3. This is what OpenSCAP really relies on. Yes, it is a rogue version, it was made to accommodate a set of changes that weren't part of any OVAL standard at the moment (like yamlfilecontent probe). We can't really add these changes to 5.11.2 (as they would break valid 5.11.2 content). |
|
Let me see if I understood this correctly, openscap has an OVAL that is not valid and that adds schemas that were never made into OVAL itself? |
Yep. Only the "invalid" content is part of ComplianceAsCode not OpenSCAP itself, but otherwise — correct. |
|
I mean, the probe was proposed of course and it has been approved, but the 5.11.3 release never happened. And now with OVAL reorganization is not going to: next versions are 5.12.x and 6.x.x, and we are so not ready to move forward in that direction. |
I've raised the topic anyway to the oval community repo, since with the migration and everything I believe all that info was lost |
5.11.3 was added back in commit 95577cd
|
Update the PR to 5.11.3 |
5.11.2 was added back in commit 141f6d2
I wonder if we should remove 5.11.3 though, as I believe it was never an official supported OVAL version.