I don't really know what the plan is here other than breaking
existing pluggable directories and wasting space.
We do clean this up but we can't stop and clean up all becase
we can't trust pkg doing the right thing right away?
For testing convenience you can run the scripts separately and
add standard output and only standard error will be reported
once included in system_firmware_configure() or
# pluginctl firmware_reload
In this post-valdation after passing validation we should make sure to prevent
validtion if not enabled. Contrary to IPv6 the range from/to is mandatory but
doesn't always match especially when changing the IP range or switching interface
assignments.
Traceback (most recent call last):
File "/usr/local/opnsense/scripts/filter/update_tables.py", line 85, in <module>
alias_content = alias.cached() if use_cached(alias_name) else alias.resolve()
File "/usr/local/opnsense/scripts/filter/lib/alias/__init__.py", line 180, in resolve
for address in address_parser.iter_addresses(item):
File "/usr/local/opnsense/scripts/filter/lib/alias/auth.py", line 71, in iter_addresses
self._update()
File "/usr/local/opnsense/scripts/filter/lib/alias/auth.py", line 53, in _update
for server in ovpn_status.get('server', None):
TypeError: 'NoneType' object is not iterable
Additions may be written inside opnsense/service/conf/configd.conf.d/ using a name ending in .conf
Another use-case it to "lock-down" configd access by default using a newly default action, e.g.:
[action_defaults]
allowed_groups = wheel
Although "openssl rehash" would be more portable, it doesn't seem to match FreeBSD's file layout.
The script in this commit mimics the certctl tool for the relevant parts, but spending a lot less time while doing so.
If at some point in time the certctl tool starts to behave again, we can simply trash this one and go back to the default option.
proposal for https://github.com/opnsense/core/issues/7063
Although in theory we should also be able to determine a change by looking at the alias and it siblings, it needs more parameters and is likely more difficult to read.
This commit should address the concerns of https://github.com/opnsense/core/pull/7057 by wrapping "read an alias content file" into a static method called "read_alias_file" and use it to determine change in both the resolv() {keeping track of this alias without siblings} and the one in update_tables.py {which is flushed to pf}
Add -u option for this reason as we cannot afford to abort when
otherwise locked and here it also doesn't matter. We could also
wait for the lock but this seems more beneficial and we can pick
up the correct environment as well, see 5c064a57090.
On the mirror we control prevent the use of "legacy" TLS versions
to allow for better security. This could be carried over to other
servers but since we don't controll most community servers this
could have negtive impact on availability depending on their config.
A quick sweep shows that all main functions check.sh, update.sh and
upgrade.sh use the launcher so that works as intended even from the
console. Another audit is required for other firmware scripts and
situations where e.g. opnsense-update is called manually. Ideally
all should go to launcher.sh or somehow be able to access the
required environment.
implode() dies when provided with arrays in arrays (on development),
so this is a good opportunity to extend the behavior a bit.
The consequence of this commit is that information that is not displayed
in a bootgrid, but still passed in as part of the dataset is also
searchable. This isn't a bad thing, but controllers still have
the option of constraining the amount of fields that should be
searched, as showcased here in interfacesInfoAction().
