Hello CWP Team,
First of all, I would like to sincerely thank the entire CWP development team for the impressive number of updates and improvements released recently.
I truly appreciate the time, dedication, and hard work you are putting into improving the platform, fixing issues, and strengthening server security.
As a long-time CWP user, I am very pleased to see the continuous development of the panel. Your efforts are greatly appreciated.
I would also like to ask for some clarification regarding the recent Secure Kernel changes introduced in CWP 1.30.22.
**My server configuration:**
- Operating system: CentOS 7
- Control panel: CWPpro
- Current running kernel: `3.10.0-1160.119.1.el7.x86_64`
- Default boot kernel: `3.10.0-1160.119.1.el7.cwpsec.x86_64`
I currently have a CWPpro license, but I do not have a Managed, Business, or Enterprise subscription, and I have not enabled the CWP Secure Kernel service.
After the recent updates, I received the following warning:
**Secure Kernel reinstalled**
"A distro kernel update had removed the CWP Secure Kernel from this server (installonly rotation). CWP reinstalled it (3.10.0-1160.119.1.el7.cwpsec.x86_64) and set it as the boot kernel; reboot to restore Secure Kernel protection."
When I open the Secure Kernel section in the CWP administration panel, I see the following message:
"CWP Secure Kernel is not active on this server."
The panel also indicates that this feature is available for Managed, Business, and Enterprise plans.
I checked the current kernel and boot configuration using:
`uname -r`
Result:
`3.10.0-1160.119.1.el7.x86_64`
And:
`grubby --default-kernel`
Result:
`/boot/vmlinuz-3.10.0-1160.119.1.el7.cwpsec.x86_64`
Therefore, my server is currently running the standard CentOS kernel, but the CWP Secure Kernel has automatically been configured as the default kernel for the next reboot.
**I would appreciate clarification on a few points:**
1. Is it normal and intentional for CWP 1.30.22 to automatically install the Secure Kernel and configure it as the default boot kernel, even on CWPpro servers without an active Secure Kernel subscription?
2. If I reboot my server, will it safely boot with the new CWP Secure Kernel despite the feature not being activated or included in my subscription?
3. When the Secure Kernel service is inactive, does the new kernel behave like the standard CentOS kernel, without enforcing additional security restrictions?
4. Could booting with this kernel potentially affect existing services such as Apache, Nginx, PHP-FPM, MariaDB, SSH, CSF firewall, or other server components?
5. Should users without a Secure Kernel subscription leave the automatically configured boot kernel unchanged, or is it preferable to continue using the standard CentOS kernel?
6. Is a reboot actually recommended for CWPpro users who do not subscribe to the Secure Kernel service?
My server is currently running normally, and I have not experienced any issues.
I have not rebooted it since this change, as I prefer to understand the expected behavior before making any decision that could affect a production server.
I fully understand that the purpose of these updates is to improve security and reliability. I simply want to make sure that everything will continue working correctly after the next reboot.
Any clarification from the development team would be greatly appreciated, and I believe it could also help other CWPpro users who may have noticed the same behavior.
Once again, thank you very much for your outstanding work, your continued dedication, and all the improvements you are bringing to CWP.
Keep up the excellent work!
Best regards,