Description

Best selling POP3/SMTP email .NET component for C#, VB.NET, and ASP.NET. Best selling Zip .NET component for C#, VB.NET, and ASP.NET. HTTP client component for communicating with HTTP servers.

.NET encryption component for C#, VB.NET, ASP.NET:

Symmetric Encryption: AES, ChaCha20, Blowfish, Twofish, RC2, ARC4, DES, 3DES, PBES1, PBES2.
Hash Algorithms: SHA-1, SHA256, SHA384, SHA512, MD2, MD4, MD5, HAVAL.
Hash Algorithms: RIPEMD128, RIPEMD160, RIPEMD256, RIPEMD320.
Encoding: Base64, hex, quoted-printable, URL-encoding, modBase64, base32, base58, uu, url_oauth, url_rfc1738, url_rfc2396, url_rfc3986, fingerprint, decimal.
HMAC with any supported hash algorithm: HMAC-MD5, HMAC-SHA1, etc.
Poly1305 Message Authentication Code
Password-based Key Derivation Functions: PBKDF1, PBKDF2
PKCS7 -- P7S and P7M creation, decryption, verification.
Public key encryption/decryption with digital certificates.
Digital signature creation/verification with digital certificates.
Bzip2 in-memory compression.
Encrypt / decrypt strings or byte data.
Return encrypted data as Base64, quoted-printable, or hex-encoded strings.
Hash strings or binary data using SHA1, MD2, MD5, HAVAL, SHA384, or SHA512.
Public-key encryption with digital certificates.
Create and verify digital signatures.
Pre-convert Unicode strings to ANSI (single-byte/char) before encrypting.
Pre-convert Unicode strings to any charset before encrypting, compressing, or hashing.
Base64 encode strings or byte data.
Hex-encode encode strings or byte data.
Compress strings or byte data with the BZIP2 compression algorithm.
Implements FIPS81 padding scheme for AES.
Up to 256-bit encryption is supported.
Set binary secret-key directly for symmetric encryption algorithms.
Initialization vectors.
CBC Cipher Block Chaining Mode
ECB Electronic Cookbook Mode
OFB Output Feedback Mode
CFB Cipher Feedback Mode
GCM Galois/Counter Mode (AEAD)
CTR Counter Mode
Punycode Encoding/Decoding
Generate UUIDs
Random byte data generation.
Streaming hashing (pass data to hashing functions in chunks).
Streaming encryption (pass data to encryption functions in chunks).
Thread safe.

Chilkat v11.0.0 Release Notes
Backward Compatibility: This is a major version release that includes some backward incompatible changes. The web pages at Chilkat v11.0.0 Backward Incompatible Changes provide details.
New Methods and Properties: There are a many new methods and properties that have been added. Almost all are in one of the following categories:
1) For methods that pass in binary data, the equivalent method that passes the binary data in a Chilkat.BinData object is added if not already present.
2) For methods that return binary data, the equivalent method that returns the binary data in a Chilkat.BinData object is added if not already present.
3) For methods that return a newly created Chilkat object, the equivalent method is added to return the object in the final argument.Methods and properties new in v11.0.0 will be shown in green font in the online reference documentation:
Deprecated Methods: Many methods are now marked as deprecated. These methods fall into the following categories.
1) In programming languages that use CkByteData , deprecated methods passing or returning binary data will gradually be replaced with BinData over an extended period. The equivalent methods using BinData are added in this release.
2) Methods returning newly created objects are deprecated in favor of the equivalent method that returns the object in the final function argument.
* Programmers will have ample time to update applications to non-deprecated alternatives. Chilkat will include example links in the reference documentation to assist in transitioning from deprecated methods. These methods will be phased out gradually, not abruptly.
SshKey: Added the UseSshCertificate method to support SSH authentication using SSH Certificates.
Http: Added the RequireHostnameMatch property.
Http: The session log file created using the SessionLogFilename property will now include the GMT date/time in the delimiters for sending and receiving.
Crypt2: The DecryptStringENC method did not work correctly if the Crypt2.Charset property was set to “unicode”. In other words, if the utf-16 byte representation of the string was encrypted, then DecryptStringENC did not correctly decode from utf-16 after decrypting. (Note: It is very rare that anyone would choose “unicode” for the byte representation when encrypting, especially when the default Charset is already “utf-8”.)
Tar: Fixed issues on non-Windows systems having to do with directories having names with trailing SPACE chars. (I know.. who would be so insane to name a directory with a trailing SPACE char?? But it happens..) Also fixed problems where the Unicode (0xFE 0xFF) and utf-8 (0xEF 0xBB 0xBF) were literally in the filenames, which is another incredibly ridiculous thing to encounter.
Xml: Added the SetBinaryContentBd method.

Additional Information