Answer the question
In order to leave comments, you need to log in
Answer the question
In order to leave comments, you need to log in
They give you a pistol with a safety catch so you don't get hurt.
You cut it off with a grinder. Because you don't understand why you need it.
If a large number of users access the server (not to be confused with website visitors), then it is not secure.
You have an apartment where there is a laser sensor. If a laser beam hits him, he opens all the locks.
And when you come home, you insert the key with a laser into the lock, turn it and send a signal to the sensor.
But at the same time, you have a window through which you can send a laser beam, for example from the window of a neighboring house.
That is, on the one hand, you still need to guess about it, to know that you can shine a laser through the window, and to know where and why, on the other hand, in the ordinary world, no one shines a laser on other people's windows, except perhaps by accident.
So here - on the one hand 755 for all files, not necessarily a hack right away, but it's not safe, because you can use it and find a loophole.
If you want a more detailed and understandable answer - study the access rights and principles of operation of various engines on the site in order to find options for how you can use the fact that you have 755 everywhere on all files.
755 - standard permissions for any file, which are usually set when it is created (if you don't change it with umask at startup)
777 - "everyone for everything" rights. Any error in the code, any failure in the settings can take the site to /dev/null and sometimes take the system with you.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question