You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

  • These are the highlights of new features or additions to existing features in v5.0.x and 5.1.x. For the complete list of all changes see this JIRA Release Notes.

TLS

We continue to improve our TLS (HTTPS) features and support. Noteworthy in 5.2.x is:

  • Dynamic TLS record size tuning.
  • Add forward secrecy support with DHE.
  • Add ssl_pre_handshake hook for better plugin access to SSL handling.
  • Improved session cache, for better performance and scalability

Jira: TS-2956, TS-3080

Minor Changes

 


Minor Changes

traffic_line can now do VIA string decoding.

Usage:

  traffic_line --decode_via <via-string-here>

Jira: TS-2904

Many potential bugs were fixed by using Co-Verity and clang static checks.

A lot of work was done at a mini-summit during the summer

Jira: TS-1475

Support for TOS setting on TCP sockets.

Jira: TS-2995

Log filters on IP fields works

Log fields that are IP address can be used for log filters. This can be done per IP address or by range

Jira: TS-698

Base string for stripe assignment allocation is now configurable

This is a maintenance feature to help preserve the cache when the operating system paths to the storage devices changes.

Jira: TS-3000

Developer Changes

  • xptr was removed and replaced with ats_scoped_str, ats_scoped_obj and ats_scoped_ptr for temporarily or contingently allocated resources.
  • The Doc header was changed to store per object version information.
  • traffic_manager was moved to the cmd directory.
  • libutils was merged in to libmgmt.
  • WebMgmtUtils moved to libmgmt.

5.1.1 Security Update

Due to security issues in 5.1.0, a possibly incompatible change was made to 5.1.1.

CVE-2014-3566 details a security vulnerability in SSL v3. Traffic Server was updated to disable SSL v3 in the default configuration. Explicit administrator action is required to enable user agents to use SSL v3 to connect to Traffic Server. SSL v3 is a very old protocol and should not be used and Traffic Server recommends leaving SSL v3 disabled.

CVW-2014-3624 details a potential Traffic Server vulnerability due to a change in how remap works This error has been fixed (TS-2677) in version 5.1.1 and requires no action on the part of the administrator beyond installing 5.1.1.

5.1.2 Security Update

Due to security issues in 5.1.1 a 5.1.2 release has been issued. It should require no changes to replace 5.1.1.

 

 

  • No labels