Tonight (23/07/19-24/07/19) the following updated packages are being released:
All packages released into the Community last week are being pushed into Business and Home.
Delayed
Packages available for testing
Packages available for testing can be installed with:
Packages being worked on:
- app-dhcp - tweak to the TFTP set up by Todd Lewis
- app-configuration-backup - add Kopano configs to backup
All packages released into the Community last week are being pushed into Business and Home.
Delayed
- app-dynamic-vpn - move the updown scripts to from the global conf file to the individual conns. This allows the Dynamic VPN and Static VPN apps to work at the same time. Also some config tidy-ups. The app is ready and tested. It just needs to be pushed to the repos but this has hit a glitch.
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)
- app-openldap-core to allow the Directory Server to publish policies for ldap:// on 389 as well as ldaps:// on 636. Please see this post.
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 - waiting on a code merge
- yum-marketplace-plugin - Enable marketplace to work when behind a proxy
Share this post:
Responses (1)
-
Accepted Answer
I have an update for the Directory Server app for testing (actually the directory server app is not touched but it affects what you can do in the Publish Policies panel of the Directory Server webconfig). This update allows you to Publish Policies for the non-secure ldap:// port (389). Up to now you could only enable Published Policies for the secure ldaps:// port 636. This is a facility that has been requested surprisingly often. ClearOS always recommend you to use ldaps:// where possible, preferring it to ldap://.
Anyway, if you want to try the update, please can you do:yum update app-openldap-core --enablerepo=clearos-updates-testing
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 »