AboutSummaryRefsLogTreeCommitDiffStats
path: root/src/crontab-access.c.in
diff options
context:
space:
mode:
authorDale Mellor <mcron-lsfnyl@rdmp.org>2023-03-18 14:18:17 +0000
committerDale Mellor <mcron-lsfnyl@rdmp.org>2023-03-18 14:18:17 +0000
commit0fe4d2cc9544d24ecc3e74a2d92433e01b9e25c6 (patch)
tree2cf2ffe793211a8c48ff86a9db57b156f2cddd88 /src/crontab-access.c.in
parentfd19e63490e30fb5ae4cc159f72b8f40952ceb9d (diff)
parent4727c770c2a723d46b4162cff21ab8f0b75c3998 (diff)
downloadmcron-0fe4d2cc9544d24ecc3e74a2d92433e01b9e25c6.tar.gz
mcron-0fe4d2cc9544d24ecc3e74a2d92433e01b9e25c6.tar.bz2
mcron-0fe4d2cc9544d24ecc3e74a2d92433e01b9e25c6.zip
Merge system-wide Vixie cron updates.
I don't believe that anyone should be running system-wide cron processes these days (the attack surface is rather large), but should use separate per-user or per-service mcron daemon processes. But mcron is advertised as a drop-in Vixie replacement, so we should do what we can to make it safe in this use case. I've performed a basic vetting of the changes against vandalism, but haven't verified the correctness of the code or done any checking; the changes are being accepted on the basis that almost anything is an improvement on what currently exists.
Diffstat (limited to 'src/crontab-access.c.in')
-rw-r--r--src/crontab-access.c.in10
1 files changed, 10 insertions, 0 deletions
diff --git a/src/crontab-access.c.in b/src/crontab-access.c.in
new file mode 100644
index 0000000..652b9cc
--- /dev/null
+++ b/src/crontab-access.c.in
@@ -0,0 +1,10 @@
+#include <unistd.h>
+
+int main(int argc, char **argv)
+{
+ char *envp = NULL;
+ execve("%libexecdir%/crontab-access-real",
+ argv, &envp);
+ /* Should not get here! */
+ return 1;
+}