{"id":13879,"date":"2019-04-06T13:19:21","date_gmt":"2019-04-06T13:19:21","guid":{"rendered":"http:\/\/www.appservgrid.com\/paw92\/?p=13879"},"modified":"2019-04-06T13:19:21","modified_gmt":"2019-04-06T13:19:21","slug":"how-to-fix-username-is-not-in-the-sudoers-file-this-incident-will-be-reported-in-ubuntu","status":"publish","type":"post","link":"https:\/\/www.appservgrid.com\/paw92\/index.php\/2019\/04\/06\/how-to-fix-username-is-not-in-the-sudoers-file-this-incident-will-be-reported-in-ubuntu\/","title":{"rendered":"How to Fix \u201cUsername is not in the sudoers file. This incident will be reported\u201d in Ubuntu"},"content":{"rendered":"

In Unix\/Linux systems, the\u00a0root<\/code>\u00a0user account is the super user account, and it can therefore be used to do anything and everything achievable on the system.<\/p>\n

However, this can be very dangerous in so many ways \u2013 one could be that the\u00a0root<\/strong>\u00a0user might enter a wrong command and breaks the whole system or an attacker gets access to root user account and takes control of the whole system and who knows what he\/she can possibly do.<\/p>\n

Based upon this background, in\u00a0Ubuntu<\/strong>\u00a0and its derivatives, the\u00a0root<\/strong>\u00a0user account is locked by default, regular users (system administrators or not) can only gain super user privileges by using the\u00a0sudo<\/code>\u00a0command.<\/p>\n

And one of the worst things that can happen to a Ubuntu System admin is losing privileges to use the\u00a0sudo<\/strong>command, a situation commonly referred to as \u201cbroken sudo<\/strong>\u201d. This can be absolutely devastating.<\/p>\n

A broken\u00a0sudo<\/strong>\u00a0may be caused by any of the following:<\/p>\n

    \n
  1. A user should not have been removed from the\u00a0sudo<\/strong>\u00a0or\u00a0admin<\/strong>\u00a0group.<\/li>\n
  2. The\u00a0\/etc\/sudoers<\/strong>\u00a0file was altered to prevent users in\u00a0sudo<\/strong>\u00a0or\u00a0admin<\/strong>\u00a0group from elevating their privileges to that of\u00a0root<\/strong>\u00a0using\u00a0sudo<\/strong>\u00a0command.<\/li>\n
  3. The permission on\u00a0\/etc\/sudoers<\/strong>\u00a0file is not set to\u00a00440<\/strong>.<\/li>\n<\/ol>\n

    In order to perform crucial tasks on your system such as viewing or altering important system files, or updating the system, you need the\u00a0sudo<\/strong>\u00a0command to gain super user privileges. What if you are denied usage of\u00a0sudo<\/strong>due one or more of the reasons we mentioned above.<\/p>\n

    Below is an image showing a case in which the default system user is being prevented from running\u00a0sudo<\/strong>command:<\/p>\n

    tecmint@TecMint ~ $<\/strong> sudo visudo\r\n[ sudo ] password for aaronkilik:\r\naaronkilik is not in the sudoers file.   This incident will be reported.\r\n\r\ntecmint@TecMint ~ $<\/strong> sudo apt install vim\r\n[ sudo ] password for aaronkilik:\r\naaronkilik is not in the sudoers file.   This incident will be reported.\r\n<\/pre>\n
    How To Fix Broken sudo Command in Ubuntu<\/h3>\n
    If you happen to be running only\u00a0Ubuntu<\/strong>\u00a0on your machine, after powering it, press the\u00a0Shift<\/code>\u00a0key for a few seconds to get the\u00a0Grub<\/strong>\u00a0boot menu. On the other hand, if you are running a dual-boot (Ubuntu alongside Windows<\/a>\u00a0or\u00a0Mac OS X<\/strong>), then you should see the Grub boot menu by default.<\/p>\n
    Using the\u00a0Down Arrow<\/code>, select \u201cAdvanced options for Ubuntu<\/strong>\u201d and press\u00a0Enter<\/strong>.<\/p>\n
    \n
    \"Ubuntu<\/a><\/p>\n
    Ubuntu Grub Menu<\/p>\n<\/div>\n
    You will be at the interface below, select the kernel with \u201crecovery mode<\/strong>\u201d option as below and press\u00a0Enter<\/strong>\u00a0to advance to the \u201cRecovery menu<\/strong>\u201d.<\/p>\n
    \n
    \"Ubuntu<\/a><\/p>\n
    Ubuntu Recovery Mode<\/p>\n<\/div>\n
    Below is the \u201cRecovery menu<\/strong>\u201d, indicating that the root filesystem is mounted as read-only. Move over to the line \u201croot Drop to root shell prompt<\/strong>\u201d, then hit\u00a0Enter<\/strong>.<\/p>\n
    \n
    \"Ubuntu<\/a><\/p>\n
    Ubuntu Recovery Menu \u2013 Drop to root Shell Prompt<\/p>\n<\/div>\n
    Next, press\u00a0Enter<\/strong>\u00a0for maintenance:<\/p>\n
    \n
    \"Ubuntu<\/a><\/p>\n
    Ubuntu Maintenance<\/p>\n<\/div>\n
    At this point, you should be at the\u00a0root<\/strong>\u00a0shell prompt. As we had seen before, the filesystem is mounted as read-only, therefore, to make changes to the system we need to remount is as read\/write by running the command below:<\/p>\n
    # mount -o rw,remount \/\r\n<\/pre>\n
    Solving Case #1 \u2013 Add User to sudo or admin Group<\/h4>\n
    Assuming that a user has been removed from the sudo group, to add user back to sudo group issue the command below:<\/p>\n
    # adduser username sudo\r\n<\/pre>\n
    Note<\/strong>: Remember to use the actual username on the system, for my case, it is\u00a0aaronkilik<\/strong>.<\/p>\n
    Or else, under the condition that a user has been removed from the admin group, run the following command:<\/p>\n
    # adduser username admin\r\n<\/pre>\n
    Solving Case #2 \u2013 Granting sudo Privileges to Users<\/h4>\n
    On the assumption that the\u00a0\/etc\/sudoers<\/code>\u00a0file was altered to prevent users in\u00a0sudo<\/strong>\u00a0or\u00a0admin<\/strong>\u00a0group from elevating their privileges to that of a super user, then make a backup of the\u00a0sudoers<\/strong>\u00a0files as follows:<\/p>\n
    # cp \/etc\/sudoers \/etc\/sudoers.orginal\r\n<\/pre>\n
    Subsequently, open the\u00a0sudoers<\/strong>\u00a0file.<\/p>\n
    # visudo\r\n<\/pre>\n
    and add the content below:<\/p>\n
    #\r\n# This file MUST be edited with the 'visudo' command as root.\r\n#\r\n# Please consider adding local content in \/etc\/sudoers.d\/ instead of\r\n# directly modifying this file.\r\n#\r\n# See the man page for details on how to write a sudoers file.\r\n#\r\nDefaults        env_reset\r\nDefaults        mail_badpass\r\nDefaults        secure_path=\"\/usr\/local\/sbin:\/usr\/local\/bin:\/usr\/sbi$\r\n\r\n# Host alias specification\r\n\r\n# User alias specification\r\n\r\n# Cmnd alias specification\r\n\r\n# User privilege specification\r\nroot    ALL=(ALL:ALL) ALL\r\n\r\n# Members of the admin group may gain root privileges\r\n%admin ALL=(ALL) ALL\r\n\r\n# Allow members of group sudo to execute any command\r\n%sudo   ALL=(ALL:ALL) ALL\r\n\r\n# See sudoers(5) for more information on \"#include\" directives:\r\n\r\n#includedir \/etc\/sudoers.d\r\n<\/pre>\n
    Solving Case #3 \u2013 Setting Correct Permission on sudoers File<\/h4>\n
    Supposing that the permission on\u00a0\/etc\/sudoers<\/strong>\u00a0file is not set to\u00a00440<\/strong>, then run following command to make it right:<\/p>\n
    # chmod  0440  \/etc\/sudoers\r\n<\/pre>\n
    Last but not least, after running all the necessary commands, type the\u00a0exit<\/code>\u00a0command to go back to the \u201cRecovery menu<\/strong>\u201d:<\/p>\n
    # exit \r\n<\/pre>\n
    Use the\u00a0Right Arrow<\/code>\u00a0to select\u00a0<Ok><\/code>\u00a0and hit\u00a0Enter<\/strong>:<\/p>\n
    \n
    \"Ubuntu<\/a><\/p>\n
    Ubuntu Recovery Menu \u2013 Resume Normal Boot<\/p>\n<\/div>\n
    Press\u00a0<Ok><\/code>\u00a0to continue with normal boot sequence:<\/p>\n
    \n
    \"Confirm<\/a><\/p>\n
    Confirm Ubuntu Normal Boot<\/p>\n<\/div>\n
    Summary<\/h3>\n
    This method should work just fine especially when it is an administrative user account involved, where there is no other option but to use the recovery mode.<\/p>\n
    However, if it fails to work for you, try to get back to us by expressing your experience via the feedback section below. You can as well offer any suggestions or other possible ways to solve the issue at hand or improve this guide altogether.<\/p>\n
    Source<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"
    In Unix\/Linux systems, the\u00a0root\u00a0user account is the super user account, and it can therefore be used to do anything and everything achievable on the system. However, this can be very dangerous in so many ways \u2013 one could be that the\u00a0root\u00a0user might enter a wrong command and breaks the whole system or an attacker gets … <\/p>\n
    Continue reading “How to Fix \u201cUsername is not in the sudoers file. This incident will be reported\u201d in Ubuntu”<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-13879","post","type-post","status-publish","format-standard","hentry","category-linux"],"_links":{"self":[{"href":"https:\/\/www.appservgrid.com\/paw92\/index.php\/wp-json\/wp\/v2\/posts\/13879","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.appservgrid.com\/paw92\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.appservgrid.com\/paw92\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.appservgrid.com\/paw92\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.appservgrid.com\/paw92\/index.php\/wp-json\/wp\/v2\/comments?post=13879"}],"version-history":[{"count":1,"href":"https:\/\/www.appservgrid.com\/paw92\/index.php\/wp-json\/wp\/v2\/posts\/13879\/revisions"}],"predecessor-version":[{"id":13880,"href":"https:\/\/www.appservgrid.com\/paw92\/index.php\/wp-json\/wp\/v2\/posts\/13879\/revisions\/13880"}],"wp:attachment":[{"href":"https:\/\/www.appservgrid.com\/paw92\/index.php\/wp-json\/wp\/v2\/media?parent=13879"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.appservgrid.com\/paw92\/index.php\/wp-json\/wp\/v2\/categories?post=13879"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.appservgrid.com\/paw92\/index.php\/wp-json\/wp\/v2\/tags?post=13879"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}