Skip to Main Content
IBM Z Hardware and Operating Systems Ideas Portal


This is the public portal for all IBM Z Hardware and Operating System related offerings. 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 updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Workspace z/OS
Created by Guest
Created on Aug 24, 2021

Collect Client Signature Algorithms with z/ERT

At the moment there is no way - besides collecting traces (AT-TLS, SystemSSL, Packettrace) to gather information about signature (hash) algorithms on TLS connections.

We would like to use z/ERT to collect data from the client hello signature algorithm extension and provide this information via NMI and write zERT SMF records.

Idea priority Medium
  • Guest
    Reply
    |
    Feb 18, 2022

    zERT is designed to describe the cryptographic protection attributes that are agreed upon and actually used on each connection.  It is not intended to show what either party is capable of  supporting.  Expanding zERT to address capabilities vs. usage would require significant design changes far beyond the client's supported signature algorithm pairs.   As pointed out in the RFE, there are other ways to collect capabilities including logs and traces.  However, it has always been understood that any changes to crytographic configuration for one end of a connection must be carefully and purposefully coordinated with the communication partner's cryptographic configuration.  This coordination should include clear communications between the responsible administrators at both ends regarding changing requirements and expectations well ahead of the time the changes are implemented.     Since IBM does not intend to expand the scope of zERT as described, we are rejecting this RFE.