DataFlex
DataFlex
SPKI Fingerprint
See more Certificates Examples
Gets the SPKI fingerprint of a certificate. In this example, the certificate object is loaded from a PEM. However, the certificate object could be obtained by any number of other means, such as by calling the GetSslServerCert method after a TLS connection has been established.Pinning is the process of associating a host with their expected X509 certificate or public key. Once a certificate or public key is known or seen for a host, the certificate or public key is associated or 'pinned' to the host. If more than one certificate or public key is acceptable, then the program holds a pinset. In this case, the advertised identity must match one of the elements in the pinset. A host or service's certificate or public key can be added to an application at development time, or it can be added upon first encountering the certificate or public key. The former - adding at development time - is preferred since preloading the certificate or public key out of band usually means the attacker cannot taint the pin. ..
Beginning in Chilkat v9.5.0.55, TLS public key pinning is implemented by (1) making it possible to easily get the SPKI fingerprint of a certificate, and (2) adding the TlsPinSet property to classes that can establish TLS connections.
Chilkat DataFlex Downloads
Use ChilkatAx-win32.pkg
Procedure Test
Boolean iSuccess
Handle hoCert
String sTemp1
Move False To iSuccess
Get Create (RefClass(cComChilkatCert)) To hoCert
If (Not(IsComObjectCreated(hoCert))) Begin
Send CreateComObject of hoCert
End
// LoadFromFile will load virtually any certificate format file.
// It will auto-recognize the format and load appropiately.
Get ComLoadFromFile Of hoCert "/Users/chilkat/testData/cer/cert.pem" To iSuccess
If (iSuccess <> True) Begin
Get ComLastErrorText Of hoCert To sTemp1
Showln sTemp1
Procedure_Return
End
// The GetSpkiFingerprint method returns the SPKI Fingerprint suitable for use in pinning.
// (See RFC 7469.) An SPKI Fingerprint is defined as the output of a known cryptographic hash
// algorithm whose input is the DER-encoded ASN.1 representation of the Subject Public Key Info
// (SPKI) of an X.509 certificate. The first argument specifies the hash algorithm and may be
// "sha256", "sha384", "sha512", "sha1", "md2", "md5", "haval", "ripemd128",
// "ripemd160","ripemd256", or "ripemd320".
// The second argument specifies the encoding, and may be "base64", "hex",
// or any of the encoding modes specified at http://www.cknotes.com/chilkat-binary-encoding-list/
// DN = "Distinguished Name"
Get ComGetSpkiFingerprint Of hoCert "sha256" "base64" To sTemp1
Showln "SPKI Fingerprint:" sTemp1
End_Procedure