В репозиторий добавлен Apache httpd 2.4.43-4 с поддержкой сжатия brotli от Google, http2 для Red Hat Enterprise Linux и CentOS. Mod_ssl собран динамически с OpenSSL 1.1.1g. Ссылки:
Заметим, что httpd 2.4.43 поддерживает TLS 1.3 при сборке с OpenSSL 1.1.1. Все новые шифры включены и работают. C версии 2.4.43-4 мы собираем OpenSSL отдельно, он устанавливается в /opt/codeit/openssl111 и никак не затрагивает системные библиотеки.
TLS 1.3 final на сегодня работает в Google Chrome 70+ и Mozilla Firefox 63+.
Для работы с SELinux в rpm включена соответствующая минимальная политика.
Модуль brotli уже включён в базовый RPM. Всё, что нужно — настроить фильтр
AddOutputFilterByType BROTLI_COMPRESS text/html text/plain text/xml text/css text/javascript application/javascript
Dear Friends
After installing 2.4.43-4, I have got an error with SSLCompression off after restarting httpd.service.
I would be glad for your help.
Thank you in advance for your help and support.
Sincerely
Dear User,
We disabled SSL compression on OpenSSL compilation level to avoid CRIME/BEAST vulnerabilities problems.
Just set SSLCompression off in your ssl.conf or vhosts files.
Dear Alexander
…but in my last configuration I had line SSLCompression off, but when I try to restart httpd.service I have got an error:
Setting Compression mode unsupported; not implemented by the SSL library
In the older version of your 2.4.43 it was working fine with this line.
Any idea how to resolve this?
Sincerely
Dear User,
The purpose of our builds are the new standards: fast, modern and highly secure.
We upgraded our builds to deliver OpenSSL library in a new dynamic way. Also, we disabled old and vulnerable features in it to additionally save traffic and memory.
If you want to use these older deprecated features such as compression that leads to CRIME/BEAST vulnerabilities, please use the bundled Apache httpd server from CentOS team. Alternatively, you want to use our builds, please disable the compression:
SSLCompression off
As it is not supported in this build.
Dear Alexander
I think you may not understand me like I want to 🙂 I’m using your builds from day one. I just say, that I have already used: «SSLCompression off» in all my configuration files in vhosts. In this new build 2.4.43-4 this command «SSLCompression off» is no longer recognized, so to properly run my httpd.service I needed to delete this command «SSLCompression off» from my configuration files or just add hash «#» before it.
The way you are trying to explain, to add «SSLCompression off» to my configuration files or ssl.conf is not working in this build.
For a good understanding of each other. Your build is forced to use «SSLCompression off», so there is no need to use this command anymore in any configuration files, because it’s always disabled = SSLCompression off? Is it correct?
Thank you once more for your great work.
Sincerely
Dear User,
Thanks for clarification, indeed I did not usnerstood you right.
Yes, OpenSSL library that we ship, does not support SSL compression and if you use our library, SSL compression is always off, even you do not explicitly specify «SSLCompression off».
You should not have removed the SSLCompression option.
It broke all our server when the update was done. And no warning. My Compression was always set to off.
Very angry.
But hey, I’m glad you are offering the repo free of charge.
Actually we did not removed it.
This is original Apache httpd behavior and we never had SSLCompression in sample config files and test hosts.
Please always test your configuration after upgrade with
httpd -t
And restart your server only after that. Also you can have your own staging environment with similar configuration to be less angry.
I think we will return compression support temporarily because of this regression.
I use apachectl -t
Is that why I get no return? the command is wrong?
Since when does this config is invalid then? I had SSLCompression off since 2018
I have no idea on
apachectl -t
unfortunately.Please upgrade to openssl111-1.1.1g-2 and httpd-2.4.43-5 and report if it works for your setup.
Well, I tested httpd -t and it worked.
Must be a change that happend sometime ago. Or when I switched repo for yours.
This morning my system updated to this :
httpd x86_64 2.4.43-4.codeit.el7 CodeIT 1.4 M
httpd-filesystem noarch 2.4.43-4.codeit.el7 CodeIT 29 k
httpd-tools x86_64 2.4.43-4.codeit.el7 CodeIT 94 k
mod_ssl x86_64 1:2.4.43-4.codeit.el7 CodeIT 121 k
Installing for dependencies:
openssl111-libs x86_64 1.1.1g-1.codeit.el7 CodeIT 1.4 M
Works OK right now. Won’t update manually. Thanks a lot for your help
Our server is crashing almost daily after we upgraded to 2.4.43-4. A lot of mpm errors and zend memory issues. Basically overnight the ram usage goes from 20% to 100% and everything crashes. The only solution is to keep rebooting constantly. Just updated to 2.4.43-5. Do you know what was fixed in this version?
Hello,
In 2.4.43-5 we only rebuilt it with OpenSSL compression support to return SSLCompression back.
Please check different mpms and php support for them. Usually they recommend to use php-fpm for event and preform mpms.
Hi Alexander,
I am working to fix a bug with httpd and mod_http2 (using your 2.4.43 from the centos 7 repo). I need to build an rpm with latest changes from https://github.com/icing/mod_h2 (from master) into a mod_http2.x86_64 1.15.9-x.codeit @CodeIT or similair
would be good that I use your script for that (to speed up the build) so I can do locally. Is that something you could share? Please could you reply personally?
This will help to fix mod_http2 — https://github.com/icing/mod_h2/issues/201
Hi Dmitry,
I would suggest to simply rebuild httpd using our SRPMs provided.
https://repo.codeit.guru/packages/centos/7/SRPMS/
You do not need any scripts: everything: patches and sources tarballs are already included in openssl111 and httpd SRPMs.
hmm, you have an interesting dependancy in the mod_http2-1.15.9-1.codeit.x86_64 on the build being performed under /root/ folder, so tests fail if this process is executed from the non-root user 🙂 but so far going ok
Alexander thank you!
I was able to update the issue with mod_http2 thanks to your prompt help.
This is great.
https://github.com/icing/mod_h2/issues/201
Hi, Alexander
So there is a new 1.15.12 version of mod_http2 that fixes among other things
header parsing which prevents 431 errors when cookies number approaches 100 on Firefox and Chrome 🙂
looking forward to see that in your repos 🙂
Hi Dmitry,
Thank you for your contribution, we will release the update asap.
Will move this discussion to httpd-2.4.43 post.
Hello,
First of all, thanks for the great work.
With your packages (Apache 2.4.43 as well as Apache 2.4.41), I have not able to override umask, which is mandaroty for my use. I tried different solution without effect.
Is it related to a specific compiling option you are using?
Many thanks in advance
Hello,
No, we do not use any specific compiling options. You can check them in our SRC RPMs provided.
Hello, if I don’t set MaxConnectionsPerChild 0 or leave it as default httpd becomes unresponsive even if not high CPU or RAM usage, and after a while AH03490: scoreboard is full, not at MaxRequestWorkers.Increase ServerLimit. on error log. So, it could be caused by your additional modules or also modpagespeed from Google. Hard to say what, unless you let me know how to inspect what prevent httpd from correctly recycling children. Thanks
Hi,
about two weeks ago I replaced the CentOS httpd version with the 2.4.43 on one server that uses WebDAV. Replacement worked well as usual but now I have problems with the WebDAV connections.
Reading directory contents works but if I try to create a new file/folder I get this message in error_log:
[dav_fs:crit] [pid 8728:tid 139838229575424] (20019)DSO load failed: AH00576: The DBM driver could not be loaded
After some seaches on different sites I really don’t understand what could be the cause for that problem. I only could see that all mentioned packages and modules come with the CodeIT version so everything should be fine.
Just saw that there ist the new version 2.4.46, but after an update I still get this messages.
So has anybody an idea of what the problem could be?
Thank you very much!
Hi Link on recent here is not found!
https://codeit.guru/en_US/2020/08/apache-httpd-2-4-46-tls-1-3-brotli-alpn-http2-openssl-1-1-1g-red-hat-centos-rhel-7-mod_http2/
Regards
Thanks, fixed.