Release Notes - Version 5.x

5.0.1 (2027-07-25)

  • Fixed error: “An unknown option was passed in to libcurl”, when sending an email by setting the libcurl dependency to version 7.50.0 or later (HOSTSERVER-927).
  • Fixed duplicate security headers (X-Frame-Options , X-Content-Type-Options) returned by API (HOSTSERVER-928).
  • The Host Server will automatically fetch the RSA/2.0 key from the Registration Server if it does not already have it (HOSTSERVER-929).
  • Very old client installations that do not have an RSA public/private key will now receive the correct error code (HOSTSERVER-930). An update to TeamDrive client 5.2.0 is also required in order restore communication with the Host Server in this case.
  • Fixed error “Locking: ... before locking: ...” error generated by the S3 Daemon when synchronising log directories with the Object Store (HOSTSERVER-933).
  • Fixed a problem when exchanging the new “API Access Key” with the Registration Server (HOSTSERVER-934), see HOSTSERVER-914 below.

Note

The API call verification can no longer be disabled, the setting APIChecksumRequired is deprecated, and has been removed.

Note

The setting APISalt has also be deprecated and will be removed in a future version. HMAC hashing together with the key stored in APIAccessKey must be used in the future. Please contact TeamDrive if you need support on this issue when accessing the Host Server API.

  • The following errors that may occur during the processing of the Object Store logs have been fixed:

    [Error] [Process S3 Logs]: Data too long for column ‘StateChangeList’ at row 1 (HOSTSERVER-937)

    Record: 0, cannot get space ID from Object Key: 112063%2Fsnapshot%2F0.log (HOSTSERVER-938)

Note

Previously setting S3EnableRedirect to False disabled the processing of Object Store log files. This has been changes in version 5.0.1 because security relavent analysis is now performed on the logs.

  • When using the API log, if a request or reply is longer that 65000 bytes, the message is now trucnted to 64000 bytes (HOSTSERVER-939). This is done by removing data from the middle of the message and replacing it with: “[...]”.
  • A regression was fixed in the TeamDrive Protocol Version 1 (aka TDP v1) (HOSTSERVER-941). This protocol is only used by TeamDrive version 3 and older client.

Note

The TDP v1 is deprecated and will be phased out in a future version of the Host Server. We recommend upgrading to the latest version of the TeamDrive Client as soon as possible.

5.0.0 (2024-05-21)

  • First release for CentOS 9. Version number 5 for all server products (TeamDrive Registration Server, TeamDrive Host Server and TeamDrive Web Portal) only stands for the common CentOS 9 release. The actual functionality of the Host Server is based on the last release 4.0.8 and only includes small changes (see below).

  • Meta-data handling: improved atomic update capabilities.

  • Certain additional security features have been implemented (HOSTSERVER-885). Host Server administrators may ask TeamDrive support for details on these changes.

  • The Host Server now supports email notifications for downloaded public files (HOSTSERVER-905). The email is sent to a specific TeamDrive user as specified in the TeamDrive App. The email is sent using the Registration Server and requires version 4.7.2 or later.

  • Added support for API access checking based on HMAC hashing and a local random generated key (HOSTSERVER-914). Switch to the new implementation is automatic as soon as it is supported by the Registration Server.

  • Implemented support of user authentication tokens (HOSTSERVER-845).

  • The Host Server getStatistics() API call was failing when the client only sends a version 2000 public key (i.e. when a version 1000 key was not provided).

  • Fixed error: Operation not permitted: ‘/tmp/td-host-df.out’ (HOSTSERVER-862).

  • The newspace() API call now supports setting meta data (HOSTSERVER-906).

  • Increase the Space event log size from 2MB to 12MB (HOSTSERVER-919).

  • When downloading a published file which requires a password, the number of times you may enter an incorrect password is now limited (HOSTSERVER-847). The limit is specified by the IncorrectPasswordLimit.

    After exceeding this limit, the user is force to wait for a certain amount of time before they may try again. This delay is specified by the IncorrectPasswordDelay setting.

    The new HTML template: “too-many-fails.html”, is used to output an error when the incorrect password limit is exceeded.

  • Added new shortcut URL paths (HOSTSERVER-846):

    • apia: the admin API (statistics and creating spaces)
    • apic: the client API (data exchange using TDP v1 and TDP v3)
    • apiy: the yvva API (general API for accessing depot and space info)
    • tdhs: use ‘tdhs’ (TeamDrive Host Server) instead of ‘primespace’

  • Fixed recalc Space size when a file that is already on S3 is re-uploaded by the client (HOSTSERVER-850).

  • Moved LogFileThreshold setting to “Resouce Management”.

  • Prevent the s3d from potentially not releasing the Space log lock, and added lock timeouts to s3d and mod_pspace to prevent hanging if a lock is held too long (HOSTSERVER-920).

  • Added setting MaxFileUploadSize. This is the maximum size of files that may be uploaded to the Host Server. The default is zero, which means unlimited. This setting is enforced by the TeamDrive client.

  • Added settings VolumeCriticalCheck, VolumeCriticalFileSize and VolumeCriticalFreeSize (HOSTSERVER-900). These settings implement the “volume critical check” feature which prevents a single large upload from consuming all free disk space and thereby disrupting the operation of spaces that share the same disk volume on the Host Server. See VolumeCriticalCheck for details.

  • Fixed potential error when adding a file to the “deleted later” list (HOSTSERVER-924).