-
Hi! I am reaching out is to ask if you have any other versions of libhiredis that we can use with libapache2-mod-auth-openidc. We are having CVE with our httpd base image. When we upgrade to the latest version of httpd image, the CVE is disappeared. However, our app will not start. The error we are getting is related to redis. From the list that we can find, libhiredis0.14 (0.14.1-4) is the only version we can see. So we had to use the earlier version - httpd:2.4.56-debian-ff which work with libhiredis0.14. Here is what we have currently:
Below is what we get:
It specifically wants hiredis v0.14.0. We tried to use different version of httpd base image other than httpd:2.4.56-debian-ff. But we have not found one that works yet. In order to fix the CVE, we need to be able to find a newer version of libapache2-mod-auth-openidc that works with newer version of libhiredis. I submitted a question with redis/hiredis#1227. They do have newer version of libhiredis. I am looking for assistance from you to find out what version of httpd and libapache2-mod-auth-openidc will work with libhiredis. Any suggestions? Thanks in advance! Thanks, |
Beta Was this translation helpful? Give feedback.
Replies: 7 comments 19 replies
-
the binaries provided in the Releases assets are for stock Debian versions and they're tested with that; we don't provide builds for all possible custom container configurations out there out of the box, you'd have to build your own binaries from scratch or get it - in a supported way - through the commercial support subscriptions via [email protected] |
Beta Was this translation helpful? Give feedback.
-
The httpd:2.4.57 image is based on Debian bookworm, and bookworm has libhiredis0.14 version 0.14.1-3 (https://packages.debian.org/bookworm/libhiredis0.14), which satisfies the dependency What is the output from the |
Beta Was this translation helpful? Give feedback.
-
@hmoffatt @zandbelt Hi! I compared the one that works and the one that does not work. The one works: which does not have the same auth_openidc:warn in the logs.
The one does not work:
Any suggestions? Thanks much! |
Beta Was this translation helpful? Give feedback.
-
@hmoffatt Hi! When you said this "I don't think changing your distro will help, as it's libapache2-mod-auth-openidc itself which is warning that your configuration is not valid. There is a change from March 2023 which relates to this message." Do you mean the message?
I did notice that it was there in our splunk log before, but not any more since April or May. What changed? Does it require the app code to adjust too? That might be the place for me to make the code change? Any ideas? Thanks! |
Beta Was this translation helpful? Give feedback.
-
@hmoffatt Hi! I was trying to use alpline just to see. I am not sure what those libraries are. Dockerfile:
But getting the error below:
Reference: Please advise. Thanks! |
Beta Was this translation helpful? Give feedback.
-
there's a lot of different moving parts in this thread by now; I'd advise you to start from the latest version (download the .deb from the Releases/Assets page), deploy on both 2.4.56 (this is likely based on bullseye) and 2.4.57 (likely based on bookworm) to check the differences and avoid accessing the protected pages over plain HTTP, i.e. use HTTPs everywhere |
Beta Was this translation helpful? Give feedback.
-
@zandbelt @hmoffatt Hi! Good afternoon! I have a few of follow up questions. Which team is responsible for building the docker image? How often will that being pushed to Docker hub? https://hub.docker.com/_/httpd Thank you! |
Beta Was this translation helpful? Give feedback.
https://github.com/OpenIDC/mod_auth_openidc/releases