Skip to Main Content
Integration


This is an IBM Automation portal for Integration products. 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 Is a defect
Created by Guest
Created on Aug 3, 2023

runmqdlq should not be setuid

For some reason the runmqdlq program is a setuid program. Now that it can be run with the -c flag this is problematic. O/S Permissions (execute permissions for mqm on the full directory structure) that would not be needed by a 'normal' MQ application have to be granted in order for it to successfully read a CCDT file. Please review whether it is really still necessary to have runmqdlq be a setuid program.

Idea priority Medium
  • Admin
    Mark Taylor
    Reply
    |
    Sep 27, 2023

    This will be handled as a defect for fixing in a future version. For some reason it was missed off the list when a number of other tools' permissions were modified