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

Rocky Linux out of box support #204

Open
bluikko opened this issue Jan 13, 2025 · 5 comments · May be fixed by #205
Open

Rocky Linux out of box support #204

bluikko opened this issue Jan 13, 2025 · 5 comments · May be fixed by #205

Comments

@bluikko
Copy link
Contributor

bluikko commented Jan 13, 2025

The default configuration/bootstrap for Rocky Linux (CentOS/RHEL derivative) is missing.

If I understand right this requires changes in src/common/DefaultConfig.php for the OS string and install/server-bootstrap.php for OVAL URL.

PR will be incoming for these but I am unable to test it for quite some time.

@bluikko bluikko linked a pull request Jan 13, 2025 that will close this issue
@HavrilaJ
Copy link
Contributor

HavrilaJ commented Jan 13, 2025

Rocky is not missing as we have it there(DefaultConfig) as part of RHEL, because Rocky didn't publish their own OVALs at the time. But now as you mentioned in PR there are some OVALs from Rocky, but unfortunately they don't include correct definitions.

More inside/technical: Rocky OVAL tag <definition> -> <advisory> doesn't include tags <cve> which should be in every definition of vulnerability. If you look on Alma/RHEL/Ubuntu OVALs they have it and we are expecting it. Maybe it could be possible to parse it from <description> but I don't think it is reliable source. Maybe I will try to contact someone if they just forgot to add <cve> tag or where is the problem.

As for now for Rocky 8/9 we are getting OVALs from RHEL, because there is not better source right now. Until they(Rocky) will fix their OVAL.

@bluikko
Copy link
Contributor Author

bluikko commented Jan 13, 2025

Sorry for wasting your time then, very unexpected that they would publish data that can only be characterized as faulty. Quite disappointing.

@bluikko
Copy link
Contributor Author

bluikko commented Jan 13, 2025

I've decided I could try to investigate/push this issue with the RL team if necessary.

Looking at the XML files I see there are major differences:

  1. reference tags pointing to CVEs & RHSAs at RH website.
  2. bugzilla tags pointing to RH bugzilla.
  3. cve tags that list CVSS metrics and links to RH website.

I believe these may be the missing tags you refer to and I suspect they may have been stripped out in order to not link to RH site or RH content in general.

@HavrilaJ
Copy link
Contributor

I was currently looking at how can I contact them. But if you want to help we would be glad.

  1. i think that reference tag is there
  2. bugzilla - not needed/expected
  3. cve tag - is the issue - CVSS is fine, because we will maybe add it to pakiti. But there is no need for links to RH to be there, we only need to reliably know which cves are belonging to definition.

Oh now I see, in previous message I wrote <> tags, especially that tag CVE is missing, but it didn't show up correctly

@bluikko
Copy link
Contributor Author

bluikko commented Jan 13, 2025

I was currently looking at how can I contact them. But if you want to help we would be glad.

  1. i think that reference tag is there

You are right, it is just missing many of them. Seems they only kept the security advisory but removed CVE links.

  1. bugzilla - not needed/expected
  2. cve tag - is the issue - CVSS is fine, because we will maybe add it to pakiti. But there is no need for links to RH to be there, we only need to reliably know which cves are belonging to definition.

Oh now I see, in previous message I wrote <> tags, especially that tag CVE is missing, but it didn't show up correctly

That makes sense, I see the edited version now. Thanks. Will inform in this issue if something comes out of it.

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

Successfully merging a pull request may close this issue.

2 participants