mirror of
https://github.com/optim-enterprises-bv/secureblue.git
synced 2025-11-02 03:18:00 +00:00
docs: command correction for gpasswd (#538)
This commit is contained in:
@@ -89,18 +89,20 @@ Creating a dedicated wheel user and removing wheel from your primary user helps
|
||||
|
||||
> [!CAUTION]
|
||||
> If you do these steps out of order, it is possible to end up without the ability to administrate your system. You will not be able to use the [traditional GRUB-based method](https://linuxconfig.org/recover-reset-forgotten-linux-root-password) of fixing mistakes like this, either, as this will leave your system in a broken state. However, simply rolling back to an older snapshot of your system, should resolve the problem.
|
||||
|
||||
1. ```sudo adduser admin```
|
||||
2. ```sudo usermod -aG wheel admin```
|
||||
3. ```sudo passwd admin```
|
||||
4. ```reboot```
|
||||
>
|
||||
1. `run0`
|
||||
2. `adduser admin`
|
||||
3. `usermod -aG wheel admin`
|
||||
4. `passwd admin`
|
||||
5. `exit`
|
||||
6. `reboot`
|
||||
|
||||
> [!NOTE]
|
||||
> We log in as admin to do the final step of removing the user account's wheel privileges in order to make the operation of removing those privileges depend on having access to your admin account, and the admin account functioning correctly first.
|
||||
|
||||
5. Log in as `admin`
|
||||
6. ```gpasswd -d {your username here} wheel```
|
||||
7. ```reboot```
|
||||
6. `run0 gpasswd -d {your username here} wheel`
|
||||
7. `reboot`
|
||||
|
||||
When using a non-wheel user, you can add the user to other groups if you want. For example:
|
||||
|
||||
|
||||
Reference in New Issue
Block a user