How to configure ubuntu server (eg 20.04) the same as proxmox in terms of "security"?

Question

linux

- it's not about how to enable / configure virtualization!
If we take a ready-made iso proxmox for example 7.1, we get a human “security” setting, the so-called. There is no such thing as UAC.
no need to add sudo, no need to repeat the password every n minutes And most importantly in winscp I can edit any files in any folders and even the local terminal executes commands, and not just in putty

Nothing like this is in ubuntu

Question how to configure ubuntu so that it does not drizzle with excessive security? how exactly see above or in proxmox directly.

ps just please on the topic, leave your very important opinion that "security is good" to yourself. I need convenience.

Answer 1

Run as root if you like.

Answer 2

Based on the comment...
Proxmox is Debian with a custom kernel. You are NOT expected to do anything EXCEPT from the Web interface.
By default, a user is not created there, only the standard admin user is present (root)
Yes, you yourself should have guessed, because. it is visible in the console.
In order to work as root in the "debian branch" distribution, it is enough
to set the root password
sudo passwd root
then type su enter the root password
That's it, you are under full admin. Only this is abnormal and against the security of linux. Because in this mode, privilege escalation is not requested for programs and a bunch of other things. Plus, you can delete without confirmation, for example, any system folder
And why the hell do you even work as root in Ubuntu then ?? If this is not a test server of course

ps just please on the topic, leave your very important opinion that "security is good" to yourself. I need convenience.

This is not a convenience, but a violation of the logic of working with the OS ... if you need to install / restart the service, type in the command with sudo.
If you just need to work as a user - you don't need sudo in principle

Answer 3

thanks to all.
-I immediately googled that we first correct PermitRootLogin yes, and only then sudo passwd.
-In fact, you have to keep 2 users on Ubuntu. as a root it is convenient to edit everything in winscp. and ncadmin is needed to go through putty and the scripts work.
Root through putty does not go in the normal way. scripts (runonce) start but cannot work. they are not sharpened for root, which is what they write about - and so on through the
ps cycle, but in general I thought that this pseudoUAC can be disabled. but it turns out it's all about who to log in

Answer 4

how to configure ubuntu so that it does not drizzle with excessive security?

(I really wanted to post Barmin's patch here so that the chela would get through that security was invented for a reason :) but still restrained himself - what if this is a combat server?)