Lỗi hduser is not in the sudoers file năm 2024
|
Mục đích của hướng dẫn này là chỉ ra cách sửa lỗi RHEL7 Show Cách khắc phục lỗi này là thêm người dùng vào nhóm Trong hướng dẫn này, bạn sẽ học:
Cách khắc phục: Lỗi người dùng RHEL7 không có trong tệp Sudoers hướng dẫn từng bướcBẠN CÓ BIẾT? Bạn luôn có thể truy cập vào tài khoản root bằng cách đăng nhập bằng lệnh $ su -i
0. Không nhất thiết phải sử dụng Thông báo lỗi trông như thế này: $ sudo -i [sudo] password for linuxconfig: linuxconfig is not in the sudoers file. This incident will be reported. Nhiều người dùng có thể gặp lỗi RHEL7 User Not In Sudoers File Error trên Red Hat Enterprise Linux hoặc một bản phân phối Linux chính khác. Để khắc phục lỗi, tất cả những gì chúng ta cần làm là thêm người dùng của mình vào đúng nhóm. Nhóm chính xác sẽ phụ thuộc vào bản phân phối bạn đang sử dụng. Đối với các bản phân phối dựa trên RPM, chẳng hạn như Red Hat, CentOS, Fedora, AlmaLinux, Rocky Linux, v.v., đây sẽ là nhóm Thực hiện theo hướng dẫn từng bước bên dưới để thêm người dùng của bạn vào đúng nhóm và sửa lỗi RHEL7 User Not In Sudoers File Error.
Bớt tư tưởngTrong hướng dẫn này, chúng ta đã biết cách sửa lỗi $ su -i
8 trên RHEL7 và các hệ thống Linux dựa trên RPM và DEB khác. Cho phép sử dụng In Unix/Linux systems, the root user 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 – one could be that the root user might enter a wrong command and break the whole system or an attacker could get access to a root user account and take control of the whole system and who knows what he/she can do. Based upon this background, in Ubuntu and Ubuntu derivatives, the root user account is locked by default, regular users (system administrators or not) can only gain superuser privileges by using the sudo command. And one of the worst things that can happen to a Ubuntu System admin is losing privileges to use the sudo command, a situation commonly referred to as “broken sudo”. This can be absolutely devastating. A broken sudo may be caused by any of the following:
In order to perform crucial tasks on your system such as viewing or altering important system files, or updating the system, you need the sudo command to gain superuser privileges. What if you are denied usage of sudo due to one or more of the reasons we mentioned above. Below is an image showing a case in which the default system user is being prevented from running the sudo command: tecmint@TecMint ~ $ sudo visudo [ sudo ] password for aaronkilik: aaronkilik is not in the sudoers file. This incident will be reported. tecmint@TecMint ~ $ sudo apt install vim [ sudo ] password for aaronkilik: aaronkilik is not in the sudoers file. This incident will be reported. How To Fix Broken sudo Command in UbuntuIf you happen to be running only Ubuntu on your machine, after powering it, press the Using the mount -o rw,remount /0, select “Advanced options for Ubuntu” and press Enter. You will be at the interface below, select the kernel with the “recovery mode” option as below and press Enter to advance to the “Recovery menu”. Below is the “Recovery menu”, indicating that the root filesystem is mounted as read-only. Move over to the line “root Drop to root shell prompt”, then hit Enter. Next, press Enter for maintenance: At this point, you should be at the root shell 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: mount -o rw,remount /Solving Case1 – Add User to sudo or admin GroupAssuming that a user has been removed from the sudo group, to add the user back to the sudo group issue the command below: adduser username sudoNote: Remember to use the actual username on the system, in my case, it is aaronkilik. Or else, under the condition that a user has been removed from the admin group, run the following command: adduser username adminSolving Case2 – Granting sudo Privileges to UsersOn the assumption that the mount -o rw,remount /1 file was altered to prevent users in the sudo or admin group from elevating their privileges to that of a super user, then make a backup of the sudoers files as follows: cp /etc/sudoers /etc/sudoers.orginalSubsequently, open the sudoers file. visudoand add the content below: This file MUST be edited with the 'visudo' command as root.Please consider adding local content in /etc/sudoers.d/ instead ofdirectly modifying this file.See the man page for details on how to write a sudoers file.Defaults env_reset Defaults mail_badpass Defaults secure_path="/usr/local/sbin:/usr/local/bin:/usr/sbi$ Host alias specificationUser alias specificationCmnd alias specificationUser privilege specificationroot ALL=(ALL:ALL) ALL Members of the admin group may gain root privileges%admin ALL=(ALL) ALL Allow members of group sudo to execute any command%sudo ALL=(ALL:ALL) ALL See sudoers(5) for more information on "include" directives:includedir /etc/sudoers.dSolving Case3 – Setting Correct Permission on sudoers FileSupposing that the permission on the /etc/sudoers file is not set to 0440, then run the following command to make it right: chmod 0440 /etc/sudoersLast but not least, after running all the necessary commands, type the mount -o rw,remount /2 command to go back to the “Recovery menu”: exitUse the mount -o rw,remount /3 to select mount -o rw,remount /4 and hit Enter: Press mount -o rw,remount /4 to continue with normal boot sequence: SummaryThis 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. 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 also offer any suggestions or other possible ways to solve the issue at hand or improve this guide altogether. |
