Matching Encryption Results w/ cryptix.jce.provider.key.RawSecretKey

If you’re doing 256-bit encryption, and your "password" is a 32-character string, then it is highly likely that the binary secret key is the ASCII values of those characters. The same applies if you are doing 128-bit encryption and you have a 16-character "password". In that case, you’ll want to set the secret key by calling

Chilkt.Crypt2.SetEncodedKey(<password string here>,"ascii")

In a nutshell, you’re telling the component to copy and use the ascii characters directly as the binary secret key. Here are examples:

ASP: ASCII / ANSI Secret Key in Symmetric Encryption
SQL Server: ASCII / ANSI Secret Key in Symmetric Encryption
C#: ASCII / ANSI Secret Key in Symmetric Encryption
C++: ASCII / ANSI Secret Key in Symmetric Encryption
Delphi: ASCII / ANSI Secret Key in Symmetric Encryption
Visual FoxPro: ASCII / ANSI Secret Key in Symmetric Encryption
Java: ASCII / ANSI Secret Key in Symmetric Encryption
Perl: ASCII / ANSI Secret Key in Symmetric Encryption
Python: ASCII / ANSI Secret Key in Symmetric Encryption
Ruby: ASCII / ANSI Secret Key in Symmetric Encryption
VB.NET: ASCII / ANSI Secret Key in Symmetric Encryption
Visual Basic: ASCII / ANSI Secret Key in Symmetric Encryption
VBScript: ASCII / ANSI Secret Key in Symmetric Encryption