Title. Long,short story: creating or editing files with nano as my non-root user gives (the file) elevated privileges, like I have ran it w/ sudo or as root. And the (only) “security hole” that I can think of is a nextdns docker container running as root. That aside, its very “overkill” security-wise (cap_drop=ALL, non-root image, security_opt=no_new_privileges, etc.).
It’s like someone tried to hack me but gave up halfway. Am I right or wrong to assume this? Just curious.
Thanks in advance.
OK I see. Can you create a new file with nano and then do an “ls -l” so we can see the permissions it’s given? Also provide the output of the command “umask” as the user you’re working with.
Just did it, and it shows my sudoer username with ownership of the created file.
umaskreturns me 0002.Can you paste the line from ls -l? Sanitize the username/date/time if you need to. Example:
-rw-r–r-- 1 bolapara users 0 Nov 21 17:19 asdf
-rw-rw-r-- 1 $sudoer $sudoer $date $createdfilename.That is not an elevated permission, your user should be able to delete that file, do the same in another directory if it works it might be a permission, or more likely an attribute, problem on the directory itself or something on the path to it.
You cannot say if user able do delete the file or not. It depends on directory permissions (deleting file is modifying a directory).