Question & Answer
Question
Some of SSH client software can't connect to Guardium CLI via SSH. It happens after applying Guardium Patch Update (GPU) 9.0p200 or 8.2p230. Why does it happen? How to resolve it?
Cause
InfoSphere Guardium 9.0p200 and 8.2p230 changed the supported ciphers ( encryption algorithms ) limited to aes128-ctr, aes192-ctr, and aes256-ctr for security improvement.
Answer
If your SSH client doesn't have aes128-ctr, aes192-ctr, nor aes256-ctr, install these ciphers or use other SSH client which supports these ciphers. Then you can connect to 9.0p200 Guardium CLI via SSH client.
[{"Product":{"code":"SSMPHH","label":"IBM Security Guardium"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"--","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"9.1;8.2","Edition":"","Line of Business":{"code":"LOB24","label":"Security Software"}}]
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21670658