Re: PPM ssh2 cipher changes
Hi Andrea. Apparently there is an enhancement request for this (I don't know why as this is a major issue for US Government entities): Here's the response I received:
"This issue presents itself because of the (DISA)Security STIG that was enabled in your server. On the other hand, R&D has an issue with the same error message "fatal: no matching cipher found: client arcfour,3des-cbc server aes256-ctr,aes192-ctr,aes128-ctr", and that issue is logged as an enhancement: "QCCR1L36513 New standards require SSH2 to use AES ciphers."