Cloud Platform

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:

Post your ideas

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive a notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

If you encounter any issues accessing the Ideas portals, please send email describing the issue to ideasibm@us.ibm.com for resolution.

For more information about IBM's Ideas program visit ibm.com/ideas.

Status Future consideration
Categories ClearCase
Created by Guest
Created on Nov 7, 2019

No world writeable Clearcase Logfiles

Clearcase writes world writeabel logfiles in Directory /var/adm/rational/clearcase/log. This is a security violation and is not allowed within Commerzbank.

Use Case
Clearcase writes world writeabel logfiles in Directory /var/adm/rational/clearcase/log. This is a security violation and is not allowed within Commerzbank.
RFE ID 137963
RFE URL
RFE Product Rational ClearCase
Idea Priority High
  • Guest
    Nov 15, 2019

    The ClearCase VOB database server processes (vobrpc, vob, db) access the VOB with the "effective user ID" of the VOB owning user, and the view server processes execute with the credentials of the view owner. In order for the logs to be collected, they have to at least default to "world" writable. If you can ensure that the VOB and view owners will be a member of a single group (a "ClearCase users group") and that group will be presented on view/VOB creation as one of the first 16/32 groups, you can reprotect the logs to 664 or 660 with the owning group being the cc users group.

    The only possible fly in the ointment is the weekly log scrubbing task, which may recreate the log files as it scrubs them. A custom job can be created to reset the permissions as desired, and that job can be scheduled to run after the log scrubbing task.