| #
aa48259f
|
| 15-Apr-2024 |
Michael Osipov <michaelo@FreeBSD.org> |
periodic.conf: remove long deprecated security_daily_compat_var()
This function is documented to be gone in after 11. Time to remove this compat shim.
PR: 275296 Reviewed by: jrm (mentor) MFC afte
periodic.conf: remove long deprecated security_daily_compat_var()
This function is documented to be gone in after 11. Time to remove this compat shim.
PR: 275296 Reviewed by: jrm (mentor) MFC after: 1 month Differential Revision: https://reviews.freebsd.org/D44796
show more ...
|
| #
d0b2dbfa
|
| 16-Aug-2023 |
Warner Losh <imp@FreeBSD.org> |
Remove $FreeBSD$: one-line sh pattern
Remove /^\s*#[#!]?\s*\$FreeBSD\$.*$\n/
|
| #
81ea85a8
|
| 11-Aug-2018 |
Brad Davis <brd@FreeBSD.org> |
Move all periodic related config and scripts to usr.sbin/periodic/
This makes pkgbase easier by tagging these as CONFS so they are properly tagged as config files.
Approved by: will (mentor) Sponso
Move all periodic related config and scripts to usr.sbin/periodic/
This makes pkgbase easier by tagging these as CONFS so they are properly tagged as config files.
Approved by: will (mentor) Sponsored by: Essen Hackathon Differential Revision: https://reviews.freebsd.org/D16553
show more ...
|
| #
cc15f413
|
| 25-Aug-2017 |
Alan Somers <asomers@FreeBSD.org> |
Fix 100.chksetuid and 110.neggrpperm for mountpoints with spaces
Also, fix them for mountpoints with tabs.
PR: 48325 Reported by: pguyot@kallisys.net, aaron@baugher.biz MFC after: 3 weeks
|
| #
05ef7ed1
|
| 29-Jan-2016 |
Marius Strobl <marius@FreeBSD.org> |
Use '^[>+][^+]' instead of '^[>+]' with grep(1) when filtering the diff(1) output between two files in "new_only"-mode. Otherwise, with the default of using unified format a remnant of the header in
Use '^[>+][^+]' instead of '^[>+]' with grep(1) when filtering the diff(1) output between two files in "new_only"-mode. Otherwise, with the default of using unified format a remnant of the header in the output is the result. This is especially irritating when the two files differ but the second one is empty, amounting to the vestige of the header being the only readout. Reported by: Stefan Haemmerl
MFC after: 3 days
show more ...
|
| #
69b55c23
|
| 27-Aug-2013 |
Jeremie Le Hen <jlh@FreeBSD.org> |
Make the period of each periodic security script configurable.
There are now six additional variables weekly_status_security_enable weekly_status_security_inline weekly_status_security_output
Make the period of each periodic security script configurable.
There are now six additional variables weekly_status_security_enable weekly_status_security_inline weekly_status_security_output monthly_status_security_enable monthly_status_security_inline monthly_status_security_output alongside their existing daily counterparts. They all have the same default values.
All other "daily_status_security_${scriptname}_${whatever}" variables have been renamed to "security_status_${name}_${whatever}". A compatibility shim has been introduced for the old variable names, which we will be able to remove in 11.0-RELEASE.
"security_status_${name}_enable" is still a boolean but a new "security_status_${name}_period" allows to define the period of each script. The value is one of "daily" (the default for backward compatibility), "weekly", "monthly" and "NO".
Note that when the security periodic scripts are run directly from crontab(5) (as opposed to being called by daily or weekly periodic scripts), they will run unless the test is explicitely disabled with a "NO", either for in the "_enable" or the "_period" variable.
When the security output is not inlined, the mail subject has been changed from "$host $arg run output" to "$host $arg $period run output". For instance: myfbsd security run output -> myfbsd security daily run output I don't think this is considered as a stable API, but feel free to correct me if I'm wrong.
Finally, I will rearrange periodic.conf(5) and default/periodic.conf to put the security options in their own section. I left them in place for this commit to make reviewing easier.
Reviewed by: hackers@
show more ...
|
| #
d7883da1
|
| 22-Aug-2005 |
Colin Percival <cperciva@FreeBSD.org> |
When looking for new lines in diff output, grep for '^[>+]' instead of '^>', in order to catch both normal and unified diffs.
Problem reported by: volker at vwsoft dot com via -stable MFC after: 3 d
When looking for new lines in diff output, grep for '^[>+]' instead of '^>', in order to catch both normal and unified diffs.
Problem reported by: volker at vwsoft dot com via -stable MFC after: 3 days
show more ...
|
| #
59583bf5
|
| 23-Sep-2004 |
Joseph Koshy <jkoshy@FreeBSD.org> |
Add a knob 'daily_status_security_diff_flags' controlling the format of the 'diff' output generated during periodic(8) scripts.
Submitted by: keramida (script changes) Reviewed by: keramida (man pag
Add a knob 'daily_status_security_diff_flags' controlling the format of the 'diff' output generated during periodic(8) scripts.
Submitted by: keramida (script changes) Reviewed by: keramida (man page changes)
show more ...
|
| #
3b5ba84f
|
| 30-Jun-2003 |
Mike Makonnen <mtm@FreeBSD.org> |
Have mktemp(1) construct the temporary file name for us instead of providing a template manually.
Submitted by: Lars Eggert <larse@isi.edu>
|
| #
da509dd2
|
| 16-Nov-2002 |
Thomas Quinot <thomas@FreeBSD.org> |
Do not emit a message on stderr when one of the compared files is shorter than the other.
Reviewed by: roberto MFC after: 3 days
|
| #
cb9eff8a
|
| 25-Oct-2002 |
Thomas Quinot <thomas@FreeBSD.org> |
Factor out code across various /etc/periodic/security scripts into a separate file, /etc/periodic/security/security.functions.
Reviewed by: roberto (mentor) Approved by: re@
|