Bug ID 1207593: Secure Shell (SSH) to BIG-IP is failing

Last Modified: Mar 30, 2024

Affected Product(s):
BIG-IP TMOS(all modules)

Known Affected Versions:
17.0.0, 17.0.0.1, 17.0.0.2

Fixed In:
17.1.0

Opened: Dec 08, 2022

Severity: 4-Minor

Symptoms

Secure Shell (SSH) connection with the aes128-gcm and aes256-gcm ciphers to BIG-IP fails.

Impact

BIG-IP is unable to match the cipher requirement and an SSH connection is unable to establish.

Conditions

When you explicitly try to establish the connection using aes128-gcm and aes256-gcm ciphers.

Workaround

Make use of other ciphers (aes128-ctr,aes256-ctr,aes128-cbc,aes192-cbc,aes256-cbc) other than aes128-gcm and aes256-gcm.

Fix Information

The aes128-gcm and aes256-gcm ciphers have been added. Now, the BIG-IP will be reachable with SSH using these ciphers.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips