Tms Cryptography Pack 3521 Delphi 102 Tokyo And Delphi May 2026

uses
  System.SysUtils, TMS.Crypto.Cipher.Symmetric, TMS.Crypto.Hash;
var
AES: TTMSCryptographicSymmetricCipher;
PlainText, Key, Encrypted, Decrypted: TBytes;
begin
// AES-256 encryption
AES := TTMSCryptographicSymmetricCipher.Create(ccAES, 256, cmCBC);
try
Key := TTMSCryptographicHash.HashData(thaSHA256, TEncoding.UTF8.GetBytes('MySecretKey'));
AES.Key := Key;
AES.GenerateIV;
PlainText := TEncoding.UTF8.GetBytes('Hello Delphi 10.2 Tokyo!');
Encrypted := AES.Encrypt(PlainText);
Decrypted := AES.Decrypt(Encrypted);
WriteLn(TEncoding.UTF8.GetString(Decrypted));

finally
AES.Free;
end;
end.

Build 3521 sometimes requires manual path adjustment on Tokyo. To verify: tms cryptography pack 3521 delphi 102 tokyo and delphi

Before we proceed, let’s break down the keyword: uses System

Why does this specific combination matter?
Delphi 10.2 Tokyo introduced significant changes to the RTL (Run-Time Library) and FMX (FireMonkey) framework. Not every cryptographic pack build works with every IDE version. Build 3521 was specifically QA-tested and compiled to link perfectly against the Tokyo RTL. Using an older build might cause EInvalidPointer or missing method errors; a newer build might require a later IDE (like Delphi 11 Alexandria). finally AES

Solution: Delphi 10.2 Tokyo introduced its own System.Hash unit. TMS avoids naming conflicts by using TMS.Cryptography.Hash. Always prefix or add the TMS source folder first in the search path.