Skip to main content

Latest Kernel not up to date?

Comments

13 comments

  • cPanelMichael
    Hello :) Please let us know the output from the following command: uname -a
    Also, could you verify which version of the "Security Advisor" is installed on your system? grep "return '1." /usr/local/cpanel/Cpanel/Security/Advisor/Assessors/Kernel.pm
    Thank you.
    0
  • russelld
    [quote="cPanelMichael, post: 1631592">Hello :) Please let us know the output from the following command: uname -a
    Also, could you verify which version of the "Security Advisor" is installed on your system? grep "return '1." /usr/local/cpanel/Cpanel/Security/Advisor/Assessors/Kernel.pm
    Thank you.
    The output for uname -a was as follows: 2.6.32-531.1.2.lve1.2.54.el6.i686 #1 SMP Tue Mar 25 07:41:32 EDT 2014 i686 i686 i386 GNU/Linux Security Advisor version is '1.01.2';
    0
  • cPanelMichael
    Could you also let us know if this is a VPS (it might be related to an internal case)? Post the output from: cat /var/cpanel/envtype
    Thank you.
    0
  • russelld
    [quote="cPanelMichael, post: 1632681">Could you also let us know if this is a VPS (it might be related to an internal case)? Post the output from: cat /var/cpanel/envtype
    Thank you.
    It is a VPS and this error was not there until I installed CloudLinux. Here is what was returned standardroot@master [~]#
    0
  • cPanelMichael
    Please open a support ticket using the link in my signature so we can take a closer look. Your warning message suggests it's related to internal case 97641, but that case is isolated to Virtuozzo VMs, which does not appear to apply to your system. You can post the ticket number here so we can update this thread with the outcome. Thank you.
    0
  • russelld
    I followed your link )
    0
  • cPanelPeter cPanel Staff
    Hello, Michael meant for you to click on the "Submit a ticket here" link in his signature. Just like mine below. You may click on either one. Or you can also click Here which will do the same thing. Thank you
    0
  • russelld
    [quote="cPanelPeter, post: 1634342">Hello, Michael meant for you to click on the "Submit a ticket here" link in his signature. Just like mine below. You may click on either one. Or you can also click Here which will do the same thing. Thank you
    Thanks for clarifying. I have submitted my request.
    0
  • cPanelMichael
    [quote="russelld, post: 1634382">Thanks for clarifying. I have submitted my request.
    Feel free to let us know the ticket number so we can update this thread with the outcome. Thanks.
    0
  • russelld
    [quote="cPanelMichael, post: 1634592">Feel free to let us know the ticket number so we can update this thread with the outcome. Thanks.
    Sure. The ticket #4891113
    0
  • cPanelMichael
    To update, this issue was addressed by manually forcing an update of the /usr/local/cpanel/Cpanel/Security/Advisor/Assessors/Kernel.pm file. Thank you.
    0
  • Yogesh Singh
    Sorry for hijacking this thread. But i think a explanation on what you modified in /usr/local/cpanel/Cpanel/Security/Advisor/Assessors/Kernel.pm file will make more sense :) For me its: SSH direct root logins are permitted. Manually edit /etc/ssh/sshd_config and change PermitRootLogin to "no", then restart SSH in the "Restart SSH" area
    I have edited /etc/ssh/sshd_config and change PermitRootLogin to "no" and restarted SSH. But the warning still shows up. Went into /usr/local/cpanel/Cpanel/Security/Advisor/Assessors/SSH.pm and found the below code which is related to my issue. if ( $sshd_config->{'PermitRootLogin'} =~ m/yes/i || !$sshd_config->{'PermitRootLogin'} ) { $self->add_bad_advice( 'text' => ['SSH direct root logins are permitted.">, 'suggestion' => [ 'Manually edit /etc/ssh/sshd_config and change PermitRootLogin to "no", then restart SSH in the "[output,url,_1,Restart SSH,_2,_3]" area', $self->base_path('scripts/ressshd'), 'target', '_blank' ], ); } else { $self->add_good_advice( 'text' => ['SSH direct root logins are disabled.">, );
    Any suggestion?
    0
  • cPanelMichael
    Hello :) Internal case number 110893 is open to address an issue where Security Advisor reports $latest_kernel based on build date rather than the version number. There is currently no specific time frame available on a resolution, but you can monitor changes to "Security Advisor" at:
    0

Please sign in to leave a comment.