What about permissions in /var/run?

Question

linux

Greetings,
There is the following strange behavior on the server - after upgrading to Wheezy 7.7, after each reboot of the server, after a while, the permissions in the /var/run directory change from the default values ​​to 770 root:root. Also, I can’t log in via ssh (I had to connect a monitor) due to the fact that the pid file of the ssh daemon has different permissions from the default value, when the daemon is restarted, the following message appears:

/var/run/sshd must be owned by root and not group or world-writable.

How can this be if the resolution is 770?
And when trying to login to the server, on the client:

ssh_exchange_identification: read: Connection reset by peer

What is treated by re-setting the permissions on the pid file. The situation is extremely strange, I ran the server with rkhunter, there is nothing critical, I checked the processes - ps aux / ps ajxf, lsof, netstat, /etc/passwd, /etc/shadow - everything is in order.
Are there any thoughts or ideas?

Answer 1

I won’t say why the permissions change, but “not group or world-writable” means that the group should not have write permissions, that is, 770 is not suitable, a maximum of 750.

Answer 2

most likely some kind of start script
, see what's in cron too

Answer 3

Solved the problem by keeping track of which process changes permissions with audictl. It turned out that the task clogged in the cron, changing the rights to the folder with user files, for some reason was incorrectly executed, recursively replacing the rights in /var (before that everything was fine). The reasons for this behavior still need to be figured out, but the problem is gone.

Answer 4

If you dynamically add buttons to the page that you later want to track. You need to use the "on" function in jQuery. Because if you use the usual click(() => {}). It will only work on the original DOM. And once you re-render it, your click won't track new elements

Answer 5

use jQuery

$('body').on('click', '.publish-date-formatted', function(){
//нечто, что происходит после клика
});