Skip to Main Content
Cloud Management and AIOps

This is an IBM Automation portal for Cloud Management and AIOps 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 (

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 Planned for future release
Workspace SevOne
Created by Guest
Created on Jan 8, 2024

sshd and security ciphers that are no longer recommended by the industry

Within SSHD.conf there are older unsupported security ciphers that the industry has recommended to be mitigated.  (This was found during a network security scan)

Below is an export from SSHD.conf in its original file. 

              # Limit the Ciphers and MACs to those approved in NMS-43491 for default mode
              Ciphers aes128-cbc,aes256-cbc,aes128-ctr,aes192-ctr,aes256-ctr
              MACs hmac-sha1,hmac-sha1-96,hmac-sha2-256,hmac-sha2-512,hmac-md5,hmac-md5-96

Here is the config that I enabled that disabled / broke cluster communications:

             # Limit the Ciphers and MACs to those approved in NMS-43491 for default mode
             Ciphers aes128-ctr,aes192-ctr,aes256-ctr
             MACs mac-sha2-256,hmac-sha2-512,

Why does the SevOne backend still use hmac-md5,hmac-md5-96 ciphers?  (if you disable hmac-md5,hmac-md5-96 ciphers the cluster goes into a state where HSA's cannot communicate, VIP's fail, chronyd fails and a bunch of other issues arise.) You can safely remove hmac-sha1,hmac-sha1-96, but MD5 is absolutely needed for back end communication...

Can these older MD5 security cipher's needed for back end SevOne communicate please be addresses in a future version of SevOne by hopefully using SHA2? MAC's?


Idea priority Medium