Will Authorize.Net’s adoption of transHashSHA2 affect plugin users?

Regarding an email to Authorize.Net users, stating, “Authorize.Net is phasing out the MD5 based transHash element in favor of the SHA-256 based transHashSHA2.”

I see the Authorize.Net Payment Gateway product info claims here that “MD5 Hash not neccesary as this plugin uses AIM.”

Since this plugin’s connection settings are API keys only, I can only assume that this is also true for the Authorize.Net CIM plugin, but can anyone verify that this is also the case?

Full email body here:
“Authorize.Net is phasing out the MD5 based transHash element in favor of the SHA-256 based transHashSHA2. The setting in the Merchant Interface which controls the MD5 Hash option will be removed by the end of January 2019, and the transHash element will stop returning values at a later date to be determined.

Merchants utilizing this feature will need to work with their web developer or solutions provider to verify if they are still utilizing MD5 based hash and if still needed to move to SHA-256 hash via Signature Key.”