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 Submitted
Workspace AIX
Created by Guest
Created on Nov 29, 2024

Mitigate security risk VOLATILE TE - tsd entries after efix installation

Why is this necessary?

After applying an efix (for example security fixes) the TE (Trusted Execution) tsd.dat is modified and stanza are replace with keyword VOLATILE.

This happens for the replaced binaries (executables) and libraries, that were replaced via those efix(es).

However: The replaced (temporary) fixed binaries and libraries are not added with the right certtag and/or signature and hash_value in the tsd database for trustchk, but all replaced with type VOLATILE.  

 

Security risk: After replacing the tsd.dat stanza’s entries with type VOLATILE. The replace binaries and / or libraries, are now vulnerable. See example below.

In other words after applying a efix, we can no longer proof that the replaced binaries / or libraries are created and approved by IBM.

Also we cannot deliver evidence to our auditors that those binaries / libraries are save and not modified after installation.

 

Desired solution: Provide for every efix the right updates into the tsd.dat database.

Similar to a normal lpp update.

Idea priority Medium