Why hardware key of SAP was changed in RHEL 6 after upgrading glibc due to Ghost issue ?

Solution Verified - Updated -

Issue

SAP Enterprise 4.72 is installed on RHEL 6 and we updated it and rebooted system due to Ghost glibc security issue.
After that, hardware key of SAP was changed unexpectedly. so, we re-downloaded this key and are now using it on RHEL.

Why hardware key in SAP was changed unexpectedly during or after updating glibc ?

Environment

Red Hat Enterprise Linux 6

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content