You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When implementing communication with Adyen terminals a special sequence of encrytion steps is required. I can see that it is basically using AES-256-CBC encryption as described in the AES full example. However, it also requires you to send the a HMAC signature. Following the Adyen example the key, the HMAC key and the IV are derived using PBKDF2, however the AES implementation of CryptoSwift requires the key to be only 32 in length and not 80 as suggested in the Adyen example.
Also I am not sure how I would go about creating the HMAC signature, which probably this comes closes to.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
When implementing communication with Adyen terminals a special sequence of encrytion steps is required. I can see that it is basically using AES-256-CBC encryption as described in the AES full example. However, it also requires you to send the a HMAC signature. Following the Adyen example the key, the HMAC key and the IV are derived using PBKDF2, however the AES implementation of CryptoSwift requires the key to be only 32 in length and not 80 as suggested in the Adyen example.
Also I am not sure how I would go about creating the HMAC signature, which probably this comes closes to.
Any help is greatly appreciated!
Beta Was this translation helpful? Give feedback.
All reactions