Franco Fichtner
Franco Fichtner
Can you output this? # sh -x /etc/periodic/weekly/310.locate Cheers, Franco
If I had to guess it's hitting here: https://github.com/opnsense/core/blob/10aa7878cf5e49c2125d8752c20ca6dea048c1de/src/sbin/opnsense-shell#L48-L53 But to be frank piping to su(1) doesn't seem very elegant to me: https://github.com/opnsense/src/blob/a91e2fb9781e118d20ed07cb11c96641d56a196d/usr.sbin/periodic/etc/weekly/310.locate#L27 How does a shell expect to know...
Ok I think this executes a root shell but then wants it to run with user "nobody". This is quite inconvenient. :)
Is that the reason for piping random commands to a shell hidden behind su to a user that doesn't maybe even have a shell? What is this?
I dug a little into https://cgit.freebsd.org/src/commit/?id=d1f4b9ffabbc which lead to https://cgit.freebsd.org/src/commit/?id=56b7685ae32 which is all features not found in FreeBSD 14 branch meaning no FreeBSD before 15.0 will support this. https://www.freebsd.org/releases/15.0R/schedule/ says...
My main concern here is the burden of reviewing opnarplog.py -- it can be done but there won't be any peer review involved when not going through the FreeBSD ports...
And yes this should be BSD 2 Clause to enter at least for the plugin management files that OPNsense needs. The Python script could be any license you think is...
Ok, you need to put the license in every file you assert copyright for otherwise these will be "commercial" and no permission to be used was given. We also need...
> In my opinion it's better to put it under services, since you setup a service that constantly monitors something. If you do diagnostics, then you do it only on...