4 ms·
It really doesn't matter, its permissions are 0664 and the uid/guid are 0/0 (root.root). It may protect you in case of a mistake, your editor should warn you t
by reidrac 14y ago
It really doesn't matter, its permissions are 0664 and the uid/guid are 0/0 (root.root).
It may protect you in case of a mistake, your editor should warn you that the file is read-only.
I don't like the post, it's too complicated for small benefits (if any). Besides there's no "generic secure setup", I think it depends on what you want to do with that server (ie. making /dev/shm read only may have impact on some software).
EDIT: I think I misunderstood your comment.
- deluxaran 14y agoI tend to agree with you about the "generic secure setup". The problem with making read only some parts of the file system, as other persons said too, is when a legit application will want to access those locations, a better solution is to remove execute rights on the desired locations.