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 Functionality already exists
Categories Crypto HW
Created by Guest
Created on Nov 30, 2023

Add the ability to generate an AES DUKPT DATA encryption key similar to the K1DATA derived key for DES DUKPT

This would allow the user to be able to perform encryption operations on DATA that has been encrypted using AES-DUKPT derived keys.

Idea priority Low
  • Guest
    Reply
    |
    Apr 1, 2024
    .Client confirmed today that the function they were looking for is supported in the current releases. We may need to look at documentation to enhance clarity.
  • Guest
    Reply
    |
    Dec 4, 2023
    Thank you for submitting the RFE. Let me ask some further questions, so that we can understand what is needed.

    I will start by saying that I think our AES-DUKPT coverage leaves a lot to be explained. CSNBUKD can actually make a wide variety of keys with AES-DUKPT. Reading the rule array descriptions, the table heading for generated_key_identifier3 says ?For A-DUKPT, only K3IPEK is allowed?. What is meant is that for generated_key_identifier3 use cases, only K3IPEK is allowed. The rule array section title of ?Output key selection for generated_key_identifier3 (One, optional)? is meant to convey that.

    You can make AES CIPHER keys in the generated_key_identifier1 slot by just passing in the correct derivation_data structure according to the table in Appendix K, ?AES-DUKPT derivation data?. Note the skeleton token in generated_key_identifier1 will be checked against the derivation_data to make sure there are not any conflicts.

    Does this help or clarify anything?

    Last point; I might be mis-interpreting the RFE. You may be asking for 64-byte AES token (what we call the ?04? or legacy AES token) support in CSNBUKD. This is not an enhancement that has been assigned much value, since we anticipated people wanting to make typed / compliant keys when they use AES DUKPT, not non-compliant / untyped keys. Is this what you were asking for?

    Please let me know your thoughts.