elog sprintf() buffer overflows on ubuntu-22, posted by Konstantin Olchanski on Wed May 15 01:07:12 2024
|
I get the following compiler warnings about sprintf() buffer overflows. I suggest sprintf() should be replaced by std::string msprintf() from
midas. K.O.
|
broken http response when deployed on OpenShift, posted by Enrico Gamberini on Wed Jul 10 17:43:07 2024
|
Hello!
We're setting up ELOG on OpenShift. ELOG is installed on a Alma Linux 9 image. The container and the elog demo works fine executing the docker
image locally. |
Re: broken http response when deployed on OpenShift, posted by Enrico Gamberini on Thu Jul 11 15:25:19 2024
|
Sorry for posting again but something else came up.
Actually, building from source (elog-3.1.5-1.tar.gz) works just fine on OpenShift
too. |
|
Re: broken http response when deployed on OpenShift, posted by Laurent Jean-Rigaud on Thu Jul 11 19:15:39 2024
|
Hey Enrico,
Do you activate also all options with your build ? (pam/ldap/kb5/ssl)
Can you compare ldd command results on elogd binaries builded by yourself and the one from RPM ? |
|
Re: broken http response when deployed on OpenShift, posted by Enrico Gamberini on Mon Jul 15 09:45:56 2024
|
Hi Laurent,
Thanks, good point! I'm building a vanilla version (no extra options enabled as I'm using Webserver authentication).
3.15 RPM: |
|
Re: broken http response when deployed on OpenShift, posted by Laurent Jean-Rigaud on Tue Jul 16 00:15:12 2024
|
Enrico,
When using RPM in OpenShift, I guess all the RPM dependencies are correctly installed.
FYI, I met a problem with elogd docker built with alpine Linux image and running on Synology NAS (x86_64). The ImageMagick dependencies libs |
|
Re: broken http response when deployed on OpenShift, posted by Laurent Jean-Rigaud on Tue Jul 16 00:45:08 2024
|
Also, you have the option to rebuild RPM from SRPMS or SOURCES via ELOG buildrpm script.
You will need to install rpmbuild tools...
Options (ldap, kb5, etc) can be set from options or by editing defaults. |
HTTP headers should be parsed case insensitive, posted by André on Mon Jul 22 16:17:55 2024
|
I'm trying to run elog behind haproxy, but get the error "Invalid Content-Length in header" on posting.
As stated in the manual,
haproxy rewrites all headers to lower case. |