CPANEL-40005 - Ubuntu cPanel Security advisor still shows yum update instead of apt-get
A KernelCare update is available.
You must take one of the following actions to ensure the system is up-to-date:
- Patch the kernel (run "kcarectl --update" on the command line).
- Update the system (run "yum -y update" on the command line), and reboot the system.
-
Ubuntu does not currently support all the features of kernelcare, for example free symlink patch will not work. 0 -
Ubuntu does not currently support all the features of kernelcare, for example free symlink patch will not work.
KernelCare is installed and current running kernel version is up to date: 5.4.0-99.112 free kernel care link in advisor worked for me after reboot root@server2:~# kcarectl --update Updates already downloaded No updates are needed for this kernel Kernel is safe its working after soft reboot, 102.2 i just installed it0 -
just FYI Verified Jailed Apache is enabled Apache Symlink Protection is enabled cPHulk Brute Force Protection is enabled. KernelCare is installed and current running kernel version is up to date: 5.4.0-99.112 MySQL test database does not exist. MySQL check for anonymous users MySQL is listening only on a local address. Password strength requirements are strong. The system did not detect processes with outdated binaries. SCGI is disabled, currently using the recommended suEXEC. The pseudo-user "nobody" is not permitted to send email. Outbound SMTP connections are restricted. Apache is being queried to determine the actual sender when mail originates from the "nobody" pseudo-user. SSH password authentication is disabled. Current SSH version is up to date: 1:8.2p1-4ubuntu0.40 -
@Spirogg - at this point we don't plan to have a separate area of the Forums specifically for Ubuntu issues, so the normal areas are still fine. I've made case CPANEL-40005 for our developers to look into that interface issue on Ubuntu, and I'll post here once I have some updates. Thanks for reporting this! 0 -
Update - this wording is going to be changed in a future build of version 102. 0 -
Update - this will be resolved in version 102.0.7 0
Please sign in to leave a comment.
Comments
6 comments