To install this update please follow these steps:
1. Go to "System -> System Operation -> Software -> System Update" and click "Get Package List" . The successful update of the package list is indicated by the message "Done!" .
2. Click "Get Packages" . This action downloads the listed update packages.
Important: If you download the packages over a slow connection (ISDN, analog, etc.), the browser may drop the connection to the administration interface. However, the download will continue in the background. Continue with the next step. If you get an error message, wait a few minutes and try again.
3. Click "Install" . This action installs the update. The end of this process is indicated by the message "Done!" .
4. The update installs a new kernel. Therefore, the system must be rebooted after installing the update: "System -> System Management -> Shutdown/Reboot -> General" .
Installation
New in this Release
Notes
Restrictions
If your Collax Business Server version is below 2.0.0 please make sure that you do a backup of the intermediate Version 1.18b. To upgrade to the current version a further intermediate step to version 2.5.2 will be accomplished.
If the version of your Collax Business Server is lower than 1.1.6a or 2.0.24, please contact the support hotline for upgrading to the latest version.
With this software the version 0.8.2-15 build 5083 of Open-Xchange groupware will be secured. This new version includes modifications for the Java Development Kit (JDK).
Assigned Common Vulnerabilities and Exposures (CVE) numbers: CVE-2006-6731, CVE-2006-6736, CVE-2006-6737, CVE-2006-6745
Note: If the add-on Open-Xchange is not installed on server version 3.0.20 this update is noneffective to the runnuing software. The version is increased to number 3.0.22 .
With this software update a new version of the Outlook-OXtender for Windows clients is available for download. The version 4.2.3 can be downloaded from https://server:8001/oxtender/outlook/ .
All web server entities of Collax servers use PHP safe mode from this update on. The following security issues are addressed:
Find details at http://www.php.net/manual/en/features.safe-mode.php
Some software needs safe mode deactivated. To deactivate PHP safe mode globally, enter the following lines as additional options to Web server -> General -> Extras.
You can also disable the safe mode for individual shares, instead of disabling globally, by writing the options like this:
Here the safe mode is disabled only for the share "TestShare".
The setting "Canonicalize sender address" can be used to rewrite internal email addresses to addresses that can be reached externally.
If you create multiple mail domains, the address is always rewritten to the first matching rewrite address. The order in which mail domains within the LDAP directory are considered for matches can change, though, and is more or less random.
You can work around this problem by configuring the email clients such that the external address is always used for outgoing e-mail.
When the authentication of users is made against a non-local database, e. g. ADS/PDC, please be aware that the user "mailadmin" does not exist on the ADS/PD, because this user is used internally in CBS. Otherwise problems will occur, e. g. during the creation of local mailboxes.
When using the web-content filter with custom lists which contain URLS and/or domains and/or expressions, it is possible that the filter is not working correctly, and doesn’t block anything. In order to fix this problem please save each list and activate the configuration.
The NTLM authentication scheme that is usually used by windows client software is now enabled when the support for windows networks has been enabled. It is no longer necessary to enable it separately.
Please note that for being able to authenticate with NTLM against a Windows 2003 Server Service Pack 1 has to be installed.
If the above error message is displayed when surfing over the web proxy and rules are used to limit the web traffic, please check the rules configured under "Settings -> Filter -> Web-Content Filter -> Rules". Load every individual rule by double-clicking the entry. If the message "Please specify at least one URL or Cobion list" is displayed, specify the respective list to be associated with this rule or enable the menu item "All". If no such error message is displayed, you can return to the list of rules by clicking "Cancel". If you changed any of the rules, activate the configuration.
All networks that are reachable through a VPN link must also be specified as reachable networks in the respective dial-in link.
It can happen, that hylafax denies facsimiles from callers. In this case, you should deactivate fax spamlists. Please follow this description: The left menu shows Messaging/Fax/General. Deactivate 'Switch on number control'. You can save now and activate the configuration.
It is possible, that problems occur when a FritzCard-AVM-PCMCIA and another different PCMCIA-card are used at the same time. In this case please call the support hotline.
In some cases it was possible that faxes were not submitted correctly so that the header was cut or missing wholly.
If you experience these problems you should set the maximum receive rate to a value below 14.400 Bit/s. You can set this in the MODEM-Page on the GUI.
In order to be able to use the Sedlbauer-ISDN-Card for an analog connection to a provider, the following must be set in "Additional Hayes-Options" : "AT&FS14=10S15=0S18=1&E" followed by the MSN of the ISDN-Card.
The configuration used within CBS works properly with the most commonly used modems. Nevertheless, it is possible that specific modems cannot be initialized correctly. At the moment, analog links are not used as fallback by the "Link monitoring" .
The AntiVir-WebGate does not yet support HTTPS which means that HTTPS-connections are not possible in combination with AntiVir-WebGate. So at the moment HTTPS-traffic bypasses this filter.
Refer to the release notes for version 3.0.0 if you update from a version older than 3.0.0.
If your CBS was installed from a CD, after this update only the first five users will be shown in the administration GUI. All other users are still existent on the system and do not affect the functionality of the server. In order to unmake these restrictions you can clear your license with our support: support@collax.com. If you own a CD-installed system or not can be seen from the text on the top of the administration GUI.
The print service itself offers its services over the Internet Printing Protocol (IPP). This protocol is directly supported by MacOS X and most Linux distributions. Printers with Ethernet ports can be added to the queues on the Collax Business Server. These printers are also exported over the printer support of the SMB/CIFS server and can be addressed directly over IPP by Windows clients.
From update 3.0.12 on, replication logs of the MySQL database are no longer written. If you need these logs, enable the option "log-bin" in the file "/etc/mysql/my.cnf.template" by removing the comment sign preceding this option. Subsequently, run a full configuration over the web interface.
To integrate the Collax Server for authentification in a Windows server network, the SMB/CIFS service can be used. It is important, that this service has at least one policy group containing a local network.
Exporting virtual hosts via FTP is only possible with IP-based virtual hosts. Name-based virtual hosting with FTP is not possible due to limitations in the FTP protocol itself.
The initial setup of the mailboxes is in conjunction with the option "Alternative namespace". This means that you should decide which format you want to use before the mailboxes are created. When this option is enabled the folders Sent, Draft and Trash are below the folder Inbox. When this option is disabled the folders Sent, Draft and Trash are on the same level as the folder Inbox. When you change the option "Alternative namespace" after the creation of the mailboxes, the Webmailer will show up a error in the following form: "Query: CREATE "INBOX.Sent" and "Reason Given: Invalid mailbox name". The name of the folder can vary.
In order to accomplish NTLM-Authorization with an imported group, this group must be a global group on the AD-Server and must be the primary group of the user.
Because of a limitation in the IPSec implementation (OpenSWAN), IPSec can only be used with four different network interfaces. In particular, this leads to problems involving failovers and outgoing IPSec connections.
You can (and must) select the interface that you will use to create a VPN link. For this link, select "dial-in" in the "initiate" field. Then, in the "on Link" field, choose the network link over which the IPSec data will be forwarded.
Additionally, if you wish to prevent these links from being used to establish an inbound connection to your local network, you must specify the system certificate as your own certificate as well as the receiver's certificate.
It is not possible to use VPN connections with asymmetric routes if the system is both a router and an IPSec gateway.
This is because IPSec accumulates a checksum of the IP header contents. With asymmetric routing, the IP addresses of the links - over which the data is transmitted and received - do not correspond.
It is not possible to establish multiple IPSec connections for the same networks and the same two security gateways. This is due to how OpenSWAN works internally (keyword "eroutes". Those having trouble with OpenSWAN know what is meant here; a deeper analysis would go beyond the scope of these release notes).
You can set up a GRE-tunnel over the IPSec-tunnel to bypass this problem.
Because VPN connections are handled as network devices some limitations apply to traffic shaping inside VPN tunnels. Specifically, this means classification information can be lost for data transmitted inside a VPN tunnel.
To use a VPN connection between a CSG and a CBS or CXS, it is necessary to disable compression for this vpn link.
The base DN of the LDAP directory cannot be changed retroactively through the GUI. The reason for this is that not all directory data can be rebuilt from the configuration.
Although data is lost, the easier way is to delete the files in the "/var/lib/openldap/openldap-data" directory, and then recreate the directory.
To achieve that, proceed as follows:
Log on to the system as "root" .
Stop the LDAP server. You can do this either through the GUI (System -> Services) or with the "/etc/init.d/openldap stop" command.
Use "cd /var/lib/openldap/openldap-data" to change to to the database directory of the LDAP server. Verify that you are in the right path with the "pwd" command.
Delete all files in the directory with "rm *.dbb" .
Change the base DN of the directory in the GUI.
Activate the changes. You will get an array of error messages explaining that data cannot be written into the LDAP directory. When the activation is completed, the LDAP server should restart with the changed configuration.
Execute the "/usr/lib/akconfig/scripts/ldif.gen config" command to transfer the data from the system configuration into the LDAP directory.
Beware: all passwords of all users will be lost after having changed the base DN. You have to enter them again via the Admin GUI.
If a transparent web proxy is activated and the Antivir Web virus scanner is activated together with the "Show download status" option, the download no longer works properly. The download progress is displayed but does not change; after a short while, the browser displays an error message indicating that antivir.webgate cannot be found. To make the download work with the progress bar, enter the proxy in the client or disable the "Show download status" option.