Skip to Main Content
IBM Power Ideas Portal


This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. 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 Under review
Workspace IBM i
Categories Security
Created by Guest
Created on Jun 14, 2024

Extend field in SSL trace output that includes cipher information

When analyzing output of SSL trace data, this may involve dumping the output to a spreadsheet for further analysis and comparison against cipher lists from QSSLCSL and/or SST (TLSCONFIG).

The challenge when comparing data is that since many cipher names are long these days, the names are truncated with part of the cipher name appearing on the next line.

There seem to be just 32 useable character spaces betweem each "*" to reflect the cipher name.

To see a related idea for enhancement, also to do with challenges when comparing cipher names, see this...

IBMI-I-4113 Make managing ciphers in QSSLCSL easier using 2-digit cipher codes and use these codes everywhere


Example:

*CONNECTION PROPERTIES *

*TLSV1.2 *

*TLS_ECDHE_RSA_WITH_CHACHA20_POLY*

*1305_SHA256 *

*LOCAL PORT *

*448 *

*LOCAL IP ADDRESS *

*::ffff:xxx.xxx.xxx.xxx *

*REMOTE PORT *

*56230 *

*REMOTE IP ADDRESS *

*::ffff:xxx.xxx.xxx.xxx *

*QRWTSRVR QUSER nnnnnn *

*QIBM_OS400_QRW_SVR_DDM_DRDA *


Phil Howells

Australia

Idea priority Medium
  • Guest
    Reply
    |
    Jul 25, 2024

    I'd like to go further and suggest that a better form of trace reporting be made available that ..

    a) provides a single line/row of information per connection and

    b) includes a date/timestamp.


    I am analyzing TLS trace data for connections using weak ciphers to determine what is the nature of the connections so that I can work with our connecting partners to uplift their client to use stronger ciphers/TLS protocols. The vertical structure of the trace data (per connection) is very hard to work with in a spreadsheet.


    Given that many security admins may need to perform extensive analysis for many systems, the challenge to work with output using this data structure is multiplied, particularly when trying to work with filters where fields containing data exist in a single column. A data structure where each piece of data for a single connection are separated out into columns in a standard reporting format would be much easier to work with and same a lot of time.

  • Guest
    Reply
    |
    Jul 12, 2024
    IBM has received your Idea and is evaluating it. IBM will provide a response after evaluation is complete.

    IBM Power Systems Development