View Issue Detail

ID	Project	Category	Submitted / Last Updated
00007	UserSpice	Feature Request	2018-03-10 21:00:50 / 2020-10-08 04:14:56
Reported	Brandin Arsenault	Assigned To	Unassigned
Priority	low	Reported	4.3.14
Status	closed fixed	Resolution Version and Commit	5.1.5
Summary	Cron Jobs overhaul
Description	<p>Theoretically, an amplification attack can happen on the cron job system. Fortunately, not a lot of users seem to use the cron job system yet. If the user is not logged in, we should check to see if it is coming from 127.0.0.1, otherwise do nothing. If logged in, use hasPerm to check for Sys Admin access.</p> <p>This was partially resolved in 4.3.11 but needs to be cooked more.</p> <p>Handle cron job timing within the actual system so cron can be called regularly throughout the day.</p>