Insalled debian as encrypted lvm wich allready created user–vg-swap_1
After converted to kicksecure swap file creator still exists .
lsblk
loop0 xxx 0 3.6G 0 loop
└─swapfile
user–vg-swap_1 xxx 976M 0 lvm
will same occur after convert if installed debian on bare metal
→ Disable
Alright.
related to
su dont work , but “su -” will work only when root account was created
sudo su works, but not secure
sudo works direct after fresh install without root account .
I think the documentation needs update somehow
No need steps 2 to 8 .
If the Debian installation was done by creating both “root” superuser and “normal” user account
(for a regular system usage), to place an order in administrator mode when the session was opened as a
“normal” user, Debian uses the “su -” command.
If the Debian installation was done with the superuser account disabled (the root password was left
empty during the installation process), the “normal” user is able to gain the superuser privilege by using
the “sudo” command.
The abstract action for the user is “become root - one way or another”.
It might be difficult to perfect the documentation because there are many different ways to install Debian.
And two options:
That’s at least 4 options.
So either su or sudo needs to be used (assuming that in some cases, Debian sets up sudo and add user “user” to group sudo by default).
If su cannot be used, just prepend all commands needing root (administative) rights with sudo. Or use sudo su.
In this context, at installation time, I don’t see any issues with that. The technical details of that are complicated. (Strong Linux User Account Isolation)