This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Specific links you will want to bookmark for future use
Support encrypted traffic between Db2 client and Db2 server using TLSv1.3
Latest version of Db2 v184.108.40.206 only has TLSv1.2 support as maximum protocol version to encrypt traffic between Db2 client and Db2 server and even this protocol is disabled by default. By default there are enabled currently insecure protocols TLSv1.0 and TLSv1.2. This is pretty conservative and insecure.
But my feature request is to add TLSv1.3 in dbm cfg parameter SSL_VERSION. https://www.ibm.com/docs/en/db2/11.5?topic=parameters-ssl-versions-supported-ssl-versions-server
TLSv1.3 is 4 years old: https://en.wikipedia.org/wiki/Transport_Layer_Security#TLS_1.3
We have been using TLSv1.3 in PostgreSQL for at least 3 years.
Microsoft SQL Server 2022 has added support support for TLS v1.3:
Do not place IBM confidential, company confidential, or personal information into any field.