User management

[Fafa24]

Hi,

I’m currently learning more about Proxmox user management. I have a few statements/questions and would appreciate your confirmation.

1. Proxmox does not use sudo by default, but with apt-get install sudo it is possible to use it.
2. root - there is no way to add another linux user and give the same rights as the root user has
3. therefore you cannot or should not disable the user root
4. Proxmox has two built-in realm: Proxmox VE and Linux PAM
5. Adding a Linux PAM user in the Proxmox GUI, requires going to the shell and add the same user with useradd
6. A Proxmox VE user has no shell access even it is a full administrator

The intention is to reduce the node's security risk without using the user root. I would rather like to use another user for the shell as root.

Thanks!

 

[Fafa24]

After my initial post and some research, I wrote an article about the Proxmox user root.

What Secrets Lie Behind the Proxmox User Root?​

Maybe this article is of some interest to you.

 

[esi_y]

After my initial post and some research, I wrote an article about the Proxmox user root.

What Secrets Lie Behind the Proxmox User Root?​

Maybe this article is of some interest to you.

I suspect installing sudo is not the greatest idea with PVE, have you thoroughly tested it?

Also, SSH PermitRootLogin no must going to break e.g. relaying, QD setup, ZFS replications.

 

[waltar]

After my initial post and some research, I wrote an article about the Proxmox user root.

What Secrets Lie Behind the Proxmox User Root?​

Maybe this article is of some interest to you.

You can create much more easily (without useradd) pve local admin users direct in "datacenter -->users" and indeed you have then shell access.
You can add an ldap realm, eg. a win AD realm, so you are not limited to the 2 defaults.
When using a pve cluster ssh "PermitRootLogin no" will break cluster services but can be circumvented with configuring for ssh and hosts.allow just between.

 

[esi_y]

When using a pve cluster ssh "PermitRootLogin no" will break cluster services but can be circumvented with configuring for ssh and hosts.allow just between.

This would imply you are running the host interface other than in a separate VLAN, which is insecure for a deployment like PVE.

 

[Fafa24]

Thank you!. I greatly appreciate it and will amend my article with the new inputs.