5.1. Regressions in 6.1.0

5.1.1. Core Libraries

5.1.1.1. XSD Issue: order enforced in <publisher> tag

This regression was introduced in 6.0.0 and has not been fixed. See XSD issue: order enforced in <publisher> tag in the 6.0.0 Regressions section.

5.1.1.2. Memory leak modifying flow_controller_name or filter_name QoS programmatically with DDS_String_dup

This regression was introduced in 6.0.0 and has not been fixed. See Memory leak modifying flow_controller_name or filter_name QoS programmatically with DDS_String_dup in the 6.0.0 Regressions section.

5.1.2. RTI Code Generator

5.1.2.1. Change in behavior in C and traditional C++ for bounded sequences under certain conditions

This regression was introduced in 6.0.0 and has not been fixed. See Change in behavior in C and traditional C++ for sequences of bounded strings under certain conditions when code is generated with optimization level 1 or 2 in the 6.0.0 Regressions section.

5.1.3. RTI TLS Support

5.1.3.1. hello_world_tcp example root and intermediate CAs expire too early

This regression was introduced in 6.1.0 and will be fixed in a future release.

In rti_workspace/examples/connext_dds/c/hello_world_tcp, the README.txt states:

Example certificates for two peers are included in dds_security/cert/tls_rsa01.

But the root CA certificate ca/rsa01RootCaCert.pem, which is the intended command-line argument for --tls-cert, expires only 30 days after it is created. The root CA certificate is therefore unusable and leads to communication failure along with the following errors:

RTITLS_ConnectionEndpointTLSv4_doHandshake:OpenSSL protocol error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed
RTITLS_ConnectionEndpointTLSv4_doHandshake:OpenSSL protocol error:14094415:SSL routines:ssl3_read_bytes:sslv3 alert certificate expired

In the identities folder, the files rsa01Peer01.pem and rsa01Peer02.pem have intermediate CAs in them, and those intermediate CAs also expire.

These problems only affect release 6.1.0 and will be fixed in an upcoming release.

As a workaround, you may use the certificates from dds_security/cert/dtls_rsa01 instead of dds_security/cert/tls_rsa01.

[RTI Issue ID COREPLG-554]