Why does Kicksecure requires a user with username user rather then anything else?
I want to create a separate Kicksecure secure hardened and no-login user(like www-data for Apache) to run Containers(podman, Docker or LXC), Proxmox or any other software.
The user already have too much privileges and I want to avoid from using it.
What should I do?
Why does Kicksecure requires a user with username user rather then anything else?
The premise that Kicksecure requires that might be wrong. What makes you think it does?
Hardcoding user names to user user has been avoided in the Kicksecure source code as much as possible.
security-misc sets up root access restrictions. Its preinst script requires that there is some user (not hardcoded to user user) that is member of the sudo group. Otherwise you’d be locked out.
Options:
- Disable login for user
user. - Try delete user
user. - Search the Source Code.
What privileges? And if so, why not remove these?
Which account are you going to use to run sudo?
Great
This applies to all of the users in group sudo right?
I want to use another user without any privileges or can’t even login to run containers, I will be using user for administration.
This applies to all of the users in group
sudoright?
Yes. Any user name is acceptable.
I want to use another user without any privileges or can’t even login to run containers, I will be using
userfor administration.
Ok.