

#no thank you lol
#no thank you lol
we’re probably talking about different things. virtually no distribution comes with root access with a password. you have to explicitly give the root user a password. without a password no amount of brute force sshing root will work. I’m not saying the root user is entirely disabled. so either the service OP is building on is basically a goldmine for compromised machines or OP literally shot themselves in the root by giving root a password manually. something you should never do.
We have it at my company its just a very small group and we have to manually enable it for production and its through tools like teleport. Staging and the like its free game there for them for debugging, same infra through. Gives us best of all worlds
Most distributions disable root by default
yeah but what about rm -rf ../../../.../var/lib/../../
?
??? Im not confusing those at all. You literally just repeated what i said.
See desktop portals, and desktop environments you dont need to use the kernel for the folder structure. And shared implantations for adding them in are fairly trivial.
sounds like a you problem. if you think longer on it maybe you’ll come up with the obvious layer to implement it at that isn’t the kernel.
Indeed they are! Just don’t need them in the filesystem itself
Userspace concept is my point dont need them in the file system itself
yes, because folders are not something thats really worthwhile in a filesystem. they’re a vestige of an earlier time.
ssh its better with the typo. ;)