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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Future consideration
Workspace PowerVM VIOS
Created by Guest
Created on Jun 17, 2022

Remove the fixed, built-in password of user vpgadmin and reduce the blast radius of the vpgadmin user

The VIOS vpgadmin user has a known pre-defined password(1), that can't be changed(2).

Although the user has login=false, and rlogin=false (3), it's a user that is part of the bin and system groups (4).

One common request of many security policies is that before a machine is put into production, all pre-defined passwords must be changed (5). Failure to do so involves risk letters and a protracted back-and-forth with the security people, to which is particularly hard to explain how 34 years after the Morris Worm, IBM thinks it's OK to ship a default password that can't be changed.

A possible solution:
- On install create a random 8-char password and stash it into a file.
- Said file should be owned by root, mode 640, and belong to a group (say group G).
- Binaries that have a need to know, belong to group G with a set-groupid flag. Password can then be read from the file without being exposed.
- One script to re-randomize the password (on every boot, or when the root user so decides)

1 - I know the password, I'm not putting it here. If I could find it, others can also.
2 - It's compiled in to at least one binary (see TS009575790), and IBM doesn't support changing it (see
3 - Having the ability to do defense in depth is a must-have for any operating systems.
4 - Being a part of the bin group allows it to replace any file in /usr/ucb, and being part of system allows it to run multiple commands with the same authority as root. A postgres instance owner should have ONE group: postgres.
5 - This is a best practice common across the industry, and was a part of IBM's own security rules until November 4, 2021.

Idea priority Urgent
  • Guest
    Jan 23, 2023
    .Need to discuss on the possibilities and the complexities in handling mixed mode clusters where UP level nodes and older level nodes exist.