Tonight (27/08/19-28/08/19) the following updated packages are being released:
All packages released into the Community two weeks ago are being pushed into Business and Home.
* = the package is also being released to Business at the same time.
Delayed
Packages available for testing
Packages available for testing can be installed with:
Packages being worked on:
- None. There has been a critical bug at gitlab.com preventing packages from building. We can now push builds through manually but it is a bit late for updates this week.
All packages released into the Community two weeks ago are being pushed into Business and Home.
* = the package is also being released to Business at the same time.
Delayed
- none
Packages available for testing
- app-network - probably not worth testing as there is a pending merge request which may cover some iof the issues found. Also you currently need to have at least two unconfigured interfaces before you can create a bridge interface in the first place. To permanently enable the Add Bridge button, you can change line 74 in /usr/clearos/apps/network/views/ifaces.php to:
This is a separate issue.if ($available_interface_count >= 0)
- yum-marketplace-plugin - should now work properly with upstream proxies
- app-software-updates - do they still work? The real test is when a updated app-base is released.
- app-attack-detector - preparation for upstream to 0.10.4. The update will back out two ClearOS changes made to jail.conf and move them to jail.local. It will also move any change made to ignoreip and reset it to default. If a jail.conf.rpmnew exists it will move jail.conf to jail.conf.rpmold and replace it with jail.conf.rpmnew. The idea behind this is that no one should be making changes to jail.conf but should put their changes in jail.local. The rpm system considers jail.conf as a config file and will not overwrite it if it has changes (hence the rpmnew). When fail2ban 0.10.4 comes out, the new jail.conf has a critical change which will break the postfix-sasl jail if jail.conf does not get updated.
- app-base - revert to upstream dnsmasq
- clamav - to upstream 0.101.4
Packages available for testing can be installed with:
yum update --enablerepo=clearos-updates-testing {package-name}
Packages being worked on:
- app-storage - another big addition of code and some fixes.
- app-network - part way through code merge
- nextcloud - upstream to 16.
- app-kopano - to prepare for upstream 8.7.5. See forum thread Update Webapp and Z-push
Share this post:
Responses (2)
-
Accepted Answer
Hi Patrick,
I am aware of those warnings, but they are only that. Both options still work but will be removed in a later release. I opted not to update to the new options as it needs a Webconfig update and I keep clear of the webconfig if I can. Also it requires a bit of a debate as which of the replacement options do we choose? -
Accepted Answer
Nick,
Not sure i've this has to with the update, but i've the following error in clam.log
WARNING: Using deprecated option "ArchiveBlockEncrypted" to alert on encrypted archives _and_ documents. Please update your configuration to use replacement options "AlertEncrypted", or "AlertEncryptedArchive" and/or "AlertEncryptedDoc".
in clamd.conf the option "ArchiveBlockEncrypted" is depreciated.
When i manually change this to "AlertEncryptedArchive", the error disappeared. This should also be in the clamd.conf (see https://github.com/opnsense/plugins/pull/1275)
When you check in the COS dashboard app "Gateway Antivirus, the option "Block Encrypted Files" is disabled. If you change this it puts back the deprecated option "ArchiveBlockEncrypted" instead of changing NO to YES
Please login to post a reply
You will need to be logged in to be able to post a reply. Login using the form on the right or register an account if you are new here.
Register Here »