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

Debian security vulnerabilities #303

Open
Kala09 opened this issue Dec 24, 2024 · 2 comments
Open

Debian security vulnerabilities #303

Kala09 opened this issue Dec 24, 2024 · 2 comments

Comments

@Kala09
Copy link

Kala09 commented Dec 24, 2024

Hi,

Is there any chance of upgrading the debian package from 11 to 12? Currently we noticed multiple security vulnerabilities in debian 11 package and the image is blocking within our organisation.

@jjethwa
Copy link
Owner

jjethwa commented Dec 24, 2024

Hi @Kala09

Thanks for creating the issue. I have some preliminary work done on updating the image here: https://github.com/jjethwa/icinga2/tree/bookworm

There does seem to be a problem with Icinga Director on the latest PHP version though, it throws a few warnings upon starting and then will throw the similar warnings in the Icinga Web 2 UI upon loading one of the Director pages the first time. Functionality seems to be unaffected once the PHP resources are compiled though. It looks like the Director team already know this and are working up update the code so it's compatible. To prevent users from having issues, I won't update the image to Debian Bookworm until Director is fully compatible.

If you don't need Director at this time, you can clone and build off the bookworm branch mentioned above. I'll keep this issue open until we can finally release it to the master branch.

@jjethwa jjethwa pinned this issue Dec 24, 2024
@jjethwa
Copy link
Owner

jjethwa commented Dec 24, 2024

Hi @Kala09

Updated the Director references and it looks like we are good to go! I'll submit a PR and push a build to latest. Let me know if you have any issues.

@jjethwa jjethwa unpinned this issue Dec 24, 2024
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

No branches or pull requests

2 participants