An asterisk (*) indicates support that was added in a hotfix or software patch subsequent to a release.

Refer to the following resources for additional information:

• Product Compatibility Guide: Provides the latest data source and platform support information. 
• Fixes: Describes the issues resolved since general availability.  
• Third-party Components Compatibility Matrix: Provides the latest information about the third-party components installed with the product.  

Version 8.0.2

Enhancements

• The driver is now compiled with a Visual Studio 2022 compiler for the Windows platforms. As a result, you must have Microsoft Visual C/C++ runtime version 14.40.33810 or higher on your machine to run the driver.
• The driver has been enhanced to support the TLSv1.3 cryptographic protocol for TLS encryption. You can configure the cryptographic protocols used by the driver with the Crypto Protocol Version (CryptoProtocolVersion) option. See  Crypto Protocol Version for details.
• The driver has been enhanced to wait a specified number of seconds to execute an OpenEdge process when encountering a locked resource. You can configure the length of the wait using the new Lock Wait Timeout (LockWaitTimeout) connection option. See  Lock Wait Timeout for details. 
• For Linux platforms only, the ICU library files that are installed with the product have been upgraded to version 74.1. In addition, the ICU library file names have changed for Linux platforms:
  • For the 32-bit driver: From libivicu27.so to libivicu.so
  • For the 64-bit driver: From libddicu27.so to libddicu.so
  This upgrade is available starting in build 08.02.0965 of the ICU library files.
• Note: OpenSSL library 3.0.9 has been replaced with a later version. For the latest information about the third-party components that are installed with the product, refer to the Third-party Components Compatibility Matrix.
  The default version of the OpenSSL library has been upgraded to version 3.0.9, which fixes the security vulnerabilities listed on the following page: https://www.openssl.org/news/vulnerabilities-3.0.html.

  Notes:

  • The driver supports the following OpenSSL 3.0 providers: Default and FIPS.
  • The FIPS provider is supported only on the following platforms: Windows 64-bit, Linux 64-bit, and AIX 64-bit.
  • When installing a new version of the product, the installer program will automatically replace the OpenSSL 1.1.1 library files with the OpenSSL 3.0 library files in the install directory, which will impact all the DataDirect ODBC drivers installed on a machine. Therefore, if you are using multiple 7.1 drivers, upgrade all your drivers to the latest version.
• A Password Encryption Tool, called ddencpwd, is now included with the product package. It encrypts passwords for secure handling in connection strings and odbc.ini files. At connection, the driver decrypts these passwords and passes them to the data source as required. See Password Encryption Tool (UNIX/Linux only) for details.
• The driver has been enhanced to support TLS/SSL server authentication for the applications deployed in a server-less environment. The driver stores the TLS/SSL certificates in memory and lets applications use TLS/SSL server authentication without storing the truststore file on the disk. To use this enhancement, specify the content of the certificate in the updated Trust Store (Truststore) connection option or the new SQL_COPT_INMEMORY_TRUSTSTORECERT pre-connection attribute.
• The driver has been enhanced to support the SQLCancel function for SELECT statements with OpenEdge V12.4 and higher. If a SELECT statement is cancelled during the first or a subsequent fetch operation, the driver returns a "query aborted" exception. This function can be used by a thread to cancel a statement that is being executed by
  another thread. One or more statements may be cancelled if the method is called on a statement object that is executing multiple statements simultaneously and the driver may not return expected results. The driver supports this function for ODBC 3.x applications only. Refer to ODBC Conformance Level for details.
  
• The Driver Manager for UNIX/Linux has been enhanced to support setting the Unicode encoding type for applications on a per connection basis. By passing a value for the SQL_ATTR_APP_UNICODE_TYPE attribute using SQLSetConnectAttr, your application can specify the encoding at connection. This allows your application to pass both UTF-8 and UTF-16 encoded strings with a single environment handle.
  The valid values for the SQL_ATTR_APP_UNICODE_TYPE attribute are SQL_DD_CP_UTF8 and SQL_DD_CP_UTF16. The default value is SQL_DD_CP_UTF8.

Changed Behavior

• The installer program now requires you to install a JRE that is Java SE 11 or higher before running the installer. In earlier versions, the JRE used by the installer program was included in the product. However, to avoid potential security vulnerabilities, the installer program no longer includes a JRE. Instead, the installer program uses the JRE in your environment to allow for the most secure version of a JRE to be used.

  Notes:

  • This change does not affect the JVM requirements for the driver. For the latest driver requirements, refer to the Product Compatibility Guide.
  • The installer program cannot remove the already installed JRE files from the install directory automatically. Remove them manually.
• The TLSv1.1 and TLSv1.0 cryptographic protocols are now disabled by default and have been removed as selectable values for the Crypto Protocol Version (CryptoProtocolVersion) option on the Setup dialog. These protocols are no longer considered secure and, therefore, are no longer recommended for use. However, the driver still supports TLSv1.1 and TLSv1.0 for legacy servers that do not support more secure protocols. See  Crypto Protocol Version for details.

Notes, Known Issues, and Limitations

• The driver does not support specifying values for the same connection option multiple times in a connection string or DSN. If a value is specified using the same attribute multiple times or using both long and short attributes, the connection may fail or the driver may not behave as intended.
• You may receive a 126 error when adding or configuring a data source stored on a network location. This is caused by the settings of the User Account Control (UAC) security feature on Windows 10. To work around this issue:
  1. From the Start menu, type regedit in the search field; then, select regedit from the results list. The Registry Editor window opens.
  2. Navigate to the following registry subkey:
     HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
  3. Right-click on the subkey; then, select New > DWORD Value.
  4. Rename the new value EnableLinkedConnections.
  5. Right-click EnableLinkedConnections, and then click Modify. The Edit DWORD Value window opens.
  6. In the Value data field, type 1. Click OK.
  7. Close the Registry Editor; then, restart your computer.
  Important: Implementing this fix disables security safeguards that are designed to protect your machine. Before starting, refer to the following Microsoft documentation for potential risks associated with disabling the UAC feature: http://windows.microsoft.com/en-us/windows/what-are-user-account-control-settings
• If you have installed an evaluation copy of the drivers and want to upgrade to a licensed version, you must use the Modify option of the installation program.
• When you first install a driver, you are given the option to install a default data source for that driver. We recommend that you install default data sources when you first install the drivers. If you do not install the default data source at this time, you will be unable to install a default data source for this driver later. To install a default data source for a driver after the initial installation, you must uninstall the driver and then reinstall it.
• When trying to connect to a database using SSL encryption, you may receive an error message similar to: "PRNG not seeded". This is because certain versions of some operating systems do not generate truly random numbers necessary for encryption. For more information about this error and available patches, please refer to the Web site:
  http://www.openssl.org/support/faq.html#USER1
  On SUSE Linux Enterprise Server 10.0, attempts by the drivers to connect using SSL Encryption will not succeed due to a problem loading the SSL libraries.
• All of the Release 8.0 Core Components (header files, etc.) needed for development of ODBC applications on UNIX and Linux are installed into the /include directory created by the product installer.
  Please read the notices file in the installation directory for licensing information regarding the ODBC Core Components. Contact your Progress DataDirect representative if you have any questions.
  Developers using programming languages other than C++: The DataDirect ODBC Driver Manager is a C++ shared library. The ODBC Driver Manager can be used with any language that supports loading a C++ shared library; however, if you are using a programming language other than C++, you must take additional steps to ensure that the C++ libraries are initialized properly when loaded. If you are not using C++, consult your compiler documentation for instructions on using C++ shared libraries with your application.
• The DataDirect ODBC Driver Manager is a C++ shared library. The ODBC Driver Manager can be used with any language that supports loading a C++ shared library; however, if you are using a programming language other than C++, you must take additional steps to ensure that the C++ libraries are initialized properly when loaded. If you are not using C++, consult your compiler documentation for instructions on using C++ shared libraries with your application.
• A default installation of the product on UNIX and Linux assumes that the value of the LANG environment setting is en_US. If your locale is not set to en_US, the drivers may not return error messages properly. In this case, you must create a symbolic link in the <Install_Dir>/locale directory that has the same value as the LANG environment setting. This link must point to the <Install_Dir>/locale/en_US directory.
• The column attributes 1001 and 1002, which were assigned as DataDirect-specific attributes, were inadvertently used as system attributes by the Microsoft 3.0 ODBC implementation. Applications using those attributes must now use 1901 and 1902, respectively.
• Because of inconsistencies in the ODBC specification, users attempting to use SQL_C_NUMERIC parameters must set the precision and scale values of the corresponding structure and the descriptor fields in the Application Parameter Descriptor.
• Some IBM AIX C compilers, such as xlc 3.1.4, do not support the use of C++ build binaries. C developers on AIX should consult their compiler documentation and verify that their AIX C compiler supports the use of C++ shared libraries or the application could be unstable.
  Unexpected behavior may occur randomly if the LIBPATH variable exceeds 178 characters AND the ORACLE_HOME variable is relatively long. To resolve this, create a shorter symbolic link for ORACLE_HOME.
• One of the most common connectivity issues encountered while using IIS (Microsoft's Internet Information Server) concerns the use and settings of the account permissions. If you encounter problems using DataDirect drivers with an IIS server, refer to KnowledgeBase document number 4274 on the Progress DataDirect web site: http://knowledgebase.datadirect.com.

Version 7.1.6

Enhancements

• The Driver Manager has been upgraded to version 8.0. The purpose of this upgrade is to have all DataDirect for ODBC drivers use the latest version of the Driver Manager, which allows for faster security updates and a consistent user experience. Note that the Driver Manager is backward compatible. As part of this upgrade:
  • The following ICU library files have been added to the product package:
    • For UNIX: libivicu28.so (32-bit) and libddicu28.so (64-bit)
    • For Linux: libivicu.so (32-bit) and libddicu.so (64-bit)
  • The trace library file names have been changed for both UNIX and Linux:
    • 32-bit: From ivtrc27.so to ivtrc28.so
    • 64-bit: From ddtrc27.so to ddtrc28.so
  Note 1: libivicu27.so (32-bit) and libddicu27.so (64-bit) will continue to be included in the product package to support driver functionality.
  Note 2: The Driver Manager build included with the product is 08.02.1997 (U1987).
• For Windows platforms, the trace library file names have been changed from ivtrc27.dll to ivtrc28.dll (32-bit) and from ddtrc27.dll to ddtrc28.dll (64-bit) to have the same file names across all platforms. This change allows for faster release of security updates and a more consistent user experience.*
  Note: To support the trace library file name change, the following ICU library files have been added to the product package: ivicu28.dll (32-bit) and ddicu28.dll (64-bit).
• The default version of the OpenSSL library has been upgraded to version 1.1.1l, which fixes the following security vulnerabilities:*
  • SM2 Decryption Buffer Overflow (CVE-2021-3711)
  • Read buffer overruns processing ASN.1 strings (CVE-2021-3712)

  Version 1.1.1l also addresses vulnerabilities resolved by earlier versions of the library. For more information on the installed library files, refer to the readme.
  For more information on the OpenSSL vulnerabilities resolved by this upgrade, refer to the corresponding OpenSSL announcements at https://www.openssl.org/news/vulnerabilities-1.1.1.html.

• OpenSSL library 1.1.1k has been replaced with version 1.1.1l. In addition to fixing multiple new vulnerabilities, version 1.1.1l also addresses the vulnerabilities resolved by version 1.1.1k:* 
  • CA certificate check bypass with X509_V_FLAG_X509_STRICT (CVE-2021-3450)
  • NULL pointer deref in signature_algorithms processing (CVE-2021-3449)
  • Null pointer deref in X509_issuer_and_serial_hash() (CVE-2021-23841)
  • Integer overflow in CipherUpdate (CVE-2021-23840) 
• OpenSSL library 1.1.1i has been replaced with version 1.1.1l. In addition to fixing multiple new vulnerabilities, version 1.1.1l also addresses the vulnerability resolved by version 1.1.1i: Incorrect behavior of the GENERAL_NAME_cmp function (CVE-2020-1971).*
• OpenSSL library 1.1.1g has been replaced with version 1.1.1l. In addition to fixing multiple new vulnerabilities, version 1.1.1l also addresses the vulnerabilities resolved by version 1.1.1g:*
  • Segmentation fault in SSL_check_chain (CVE-2020-1967)
  • rsaz_512_sqr overflow bug on x86_64 (CVE-2019-1551)  
• The drivers using base version B0649 and later have been enhanced to include timestamp in the internal packet logs by default. If you want to disable the timestamp logging in packet logs, set PacketLoggingOptions=1. The internal packet logging is not enabled by default. To enable it, set EnablePacketLogging=1.*
• OpenSSL library 1.0.2r has been replaced with version 1.0.2u. In addition to fixing multiple new vulnerabilities, version 1.0.2u also addresses the vulnerabilities resolved by version 1.0.2r.*
  Version 1.0.2u of the OpenSSL library fixes the following security vulnerabilities:
  • x64_64 Montgomery squaring procedure used in exponentiation with 512-bit moduli (CVE-2019-1563)
  • Padding Oracle in PKCS7_dataDecode and CMS_decrypt_set1_pkey (CVE-2019-1563)
  • Compute ECC cofactors if not provided during EC_GROUP construction (CVE-2019-1547)
  • Installation paths in diverse Windows builds (CVE-2019-1552)

  Note: By default, the driver will attempt to load version 1.1.1 of the library; however, if the library cannot be loaded, the driver will fall back to version 1.0.2.

• The default OpenSSL library version has been updated to 1.1.1d.*
• The default OpenSSL library version has been updated to 1.0.2r.*
• The default OpenSSL library version has been updated to 1.0.2n.*
• The default OpenSSL library version has been updated to 1.0.2k.*
• The default OpenSSL library version has been updated to 1.0.2j.*
• The default OpenSSL library version has been updated to 1.0.2h.*
• The default OpenSSL library version has been updated to 1.0.2g.*
• The default OpenSSL library version has been updated to 1.0.2f.
• The new CryptoLibName and SSLLibName connection options allow you to
  designate the OpenSSL libraries used when SSL is enabled.

Changed Behavior

• The product package no longer includes the ODBC Cursor library file (odbccurs.so) because it has some known security vulnerabilities that could potentially expose you to security risks.*
  Note: The installer program cannot remove the ODBC Cursor library file automatically while installing a new version of the driver. Remove it manually.
• The product no longer includes version 1.1.1 of the OpenSSL library. The library will reach the end of its product life cycle in September 2023 and will not receive any security updates after that. Note that continuing to use the library after September 2023 can potentially expose you to security vulnerabilities.*

  Note: As a result of this change, when installing a new version of the product, the installer program will automatically remove version 1.1.1 of the library from the install directory, which will impact all the DataDirect ODBC drivers installed on a machine.

• The product no longer includes version 1.0.2 of the OpenSSL library. The library has reached the end of its product life cycle and is not receiving security updates anymore. Note that continuing to use the library could potentially expose you to security vulnerabilities.*
  Note: As a result of this change, when installing a new version of the driver, the installer program will automatically remove version 1.0.2 of the library from the install directory.
• The Allowed OpenSSL Versions (AllowedOpenSSLVersions) connection option has been deprecated as the driver currently supports only version 3.0 of the OpenSSL library.*
• The crypto protocol versions prior to TLSv1 are no longer supported.*
  

Version 7.1.5

Enhancements

• The OpenSSL library was upgraded to version 1.0.0r, which fixes the
  CVE‐2015‐0204 (FREAK) vulnerability. See "RSA silently downgrades
  to EXPORT_RSA [Client] (CVE‐2015‐0204)" at
  https://www.openssl.org/news/secadv_20150108.txt for more
  information.
• The new Crypto Protocol Version connection option allows you to specify
  the cryptographic protocols used when SSL is enabled. This option can be
  used to avoid vulnerabilities associated with SSLv3 and SSLv2, including
  the POODLE vulnerability.

Version 7.1.4

Enhancements

• The new KeepAlive connection option allows you to use TCP Keep Alive to maintain idle TCP connections.

Version 7.1.3

No features introduced 

Version 7.1.2

No features introduced 

Version 7.1.1

No features introduced 

Version 7.1.0

No features introduced