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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
Having a single key fingerprint or checksum in the SMF data leads to collisions when trying to validate that the same key is not present in multiple environments. Having a second fingerprint in the SMF 82 40 records would help us to determine whether two keys with the same encrypt zero checksum were really the same or different. This is necessary for compliance reasons, to validate that production and non-production environments do not share any keys.
ICSF supports calculating a CMACZERO fingerprint for most key types, and the SMF 82 40 record already supports this fingerprint, so it would be the logical choice. The documentation says this is only populated for AES compliant tagged keys, so our request is that it be populated for all key types that support the CMACZERO fingerprint. Having both an encrypt zero and a CMACZERO fingerprint would give us much greater confidence that our key repositories are in compliance.
Idea priority | Medium |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
I think this is a good idea. ENC-ZERO has too many opportunities for collisions by itself in a larger installation.