Operational Defect Database

BugZero found this defect 1552 days ago.

F5 | 758491

When using NetHSM integration, after upgrade to 14.1.0 or later (or creating keys using fipskey.nethsm), BIG-IP cannot use the keys

Last update date:

4/26/2024

Affected products:

BIG-IP

BIG-IP LTM

Affected releases:

14.1.0

14.1.0.1

14.1.0.2

14.1.0.3

14.1.0.5

14.1.0.6

14.1.2

14.1.2.1

14.1.2.2

14.1.2.3

14.1.2.4

14.1.2.5

Fixed releases:

No fixed releases provided.

Description:

Bug ID 758491: When using NetHSM integration, after upgrade to 14.1.0 or later (or creating keys using fipskey.nethsm), BIG-IP cannot use the keys ... Last Modified: Apr 26, 2024 ... Conditions ... 1. Keys were created on earlier versions of BIG-IP software, no matter if using tmsh (Safenet) or using fipskey.nethsm (Thales, Safenet) and the device was upgraded to 14.1.0 or later. ... 2. Keys were created on BIG-IP v14.1.0 or later directly, using fipskey.nethsm (Thales). ... For Safenet, fipskey.nethsm was deprecated in 14.0.0. ... Workaround ... There are two workarounds: -- Re-create the keys using tmsh command. ... IMPORTANT: This workaround is suitable for deployments that are new and not in production. -- Re-import the keys from nethsm using: tmsh install sys crypto key <key_label> from-nethsm You can find the key_label here: -- The rightmost string in the output of the Thales command: nfkminfo -l -- The string after label= in the 'cmu list' command for Safenet. ... Fix Informa...

Additional Resources / Links

Share:

BugZero® Risk Score

What's this?

Coming soon

Status

New

Learn More

Search:

...