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 Delivered
Workspace AIX
Created by Guest
Created on Sep 26, 2019

Enhance performance of AIX Trusted Execution by improving the logic to verify integrity of untrusted files

Trusted Execution (TE) is an AIX security feature for file integrity verification. For performing the integrity check, TE compares the hash value of the files on the system against the pre-calculated hash values stored in its Trusted signature database (TSD). To improve performance, TE includes a logic to avoid calculating the hash value if the previous check was successful and the file is not modified after that. In this RFE we propose to extend the same logic to avoid integrity check even if the previous check was unsuccessful and the file is not modified. Because if the file is not modified then doing an integrity check again will give the same result with unnecessary performance impact.

Idea priority Medium
  • Guest
    Reply
    |
    Feb 15, 2021

    .Delivered in 7.2.5

  • Guest
    Reply
    |
    Oct 1, 2019

    Besides improving performance, another benefit of this feature is that is would eliminate duplicate messages of failing executables being reported to syslog. So as long as the files that are executed don't change, duplicate syslog messages won't be reported to syslog. Therefore the customer will more easily be able to ascertain the unique set of executables that need to be updated in order to properly meet the trusted execution runtime requirements. This will greatly facilitate TE adoption since configuring and maintaining the TSD to leverage TE's runtime kernel checking will be much easier to accomplish.

  • Guest
    Reply
    |
    Oct 1, 2019

    I think this is a great request. However, just to clarify, I think this should be an option. The customer should be able to configure either this recommended new behavior or the legacy behavior. For example: trustchk -p STREAMLINE_CHK=ON would be the new behavior, and the TE default (legacy behavior) would be trustchk -p STREAMLINE_CHK=OFF.