Chilkat supports CAdES-BES and CAdES-EPES digital signatures

Chilkat v9.3.0, being released this week, now supports the ability to create CAdES-BES and CAdES-EPES digital signatures via the MailMan, Mime, and Crypt2 objects.   All three objects/classes now include the following new properties:

bool CadesEnabled;
string CadesSigPolicyId;
string CadesSigPolicyUri;
string CadesSigPolicyHash;  (base64 encoded representation of hash)

To create a CAdES-BES signature, simply set the CadesEnabled property = true.

For CAdES-EPES, set each of the other new properties.  For example:

crypt.CadesSigPolicyId = “2.16.76.1.7.1.1.1”;
crypt.CadesSigPolicyUri = “http://politicas.icpbrasil.gov.br/PA_AD_RB.der”;
crypt.CadesSigPolicyHash = “rySugyKaMhiMR8Y/o5yuU2A2bF0=”;

If you set these properties prior to calling any method that creates a signature, then a CAdES signature is created.

How to Compute a URL Signature for the Google Maps API

Examples for computing a URL signature for the Google Maps API:

ASP: URL Signing for Google Maps API
SQL Server: URL Signing for Google Maps API
C#: URL Signing for Google Maps API
C++: URL Signing for Google Maps API
Objective-C: URL Signing for Google Maps API
PowerShell: URL Signing for Google Maps API
MFC: URL Signing for Google Maps API
C: URL Signing for Google Maps API
Delphi: URL Signing for Google Maps API
Visual FoxPro: URL Signing for Google Maps API
Java: URL Signing for Google Maps API
Perl: URL Signing for Google Maps API
PHP: URL Signing for Google Maps API
Python: URL Signing for Google Maps API
Ruby: URL Signing for Google Maps API
VB.NET: URL Signing for Google Maps API
Visual Basic: URL Signing for Google Maps API
VBScript: URL Signing for Google Maps API