(SQL Server) HTTP Public Key Pinning

Demonstrates how to specify a TLS pinset that lists the pre-known valid and accepted TLS server certificate public keys. When a TLS pinset is specified, the Chilkat TLS client software will reject TLS connections (inside the TLS handshake) when the server provides a certificate having a public key not listed in the pinset. This makes it possible to reject the connection at the earliest possible time, before any information (such as the HTTP request) has been sent to the server.

What is Pinning?

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.

Get SPKI Fingerprint using OpenSSL

This example shows how Chilkat can be used to obtain the server's public key SPKI fingerprint. OpenSSL can also get the fingerprint with these two commands (shown for the domain ssllabs.com) :

openssl x509 -noout -in ssllabs.com.pem -pubkey | openssl asn1parse -noout -inform pem -out ssllabs.com.key
openssl dgst -sha256 -binary ssllabs.com.key | openssl enc -base64

Chilkat ActiveX Downloads ActiveX for 32-bit and 64-bit Windows

-- Important: See this note about string length limitations for strings returned by sp_OAMethod calls.
--
CREATE PROCEDURE ChilkatSample
AS
BEGIN
    DECLARE @hr int
    DECLARE @iTmp0 int
    -- Important: Do not use nvarchar(max).  See the warning about using nvarchar(max).
    DECLARE @sTmp0 nvarchar(4000)
    -- This example requires the Chilkat API to have been previously unlocked.
    -- See Global Unlock Sample for sample code.

    DECLARE @httpA int
    -- Use "Chilkat_9_5_0.Http" for versions of Chilkat < 10.0.0
    EXEC @hr = sp_OACreate 'Chilkat.Http', @httpA OUT
    IF @hr <> 0
    BEGIN
        PRINT 'Failed to create ActiveX component'
        RETURN
    END

    -- To do public key pinning, the SPKI fingerprint would be obtained beforehand -- perhaps
    -- at design time, or possibly at the time of the 1st connection (where the SPKI fingerprint
    -- is persisted for future use).  Note:  "If the certificate or public key is added upon first
    -- encounter, you will be using key continuity. Key continuity can fail if the attacker has a 
    -- privileged position during the first first encounter." 
    -- See https://www.owasp.org/index.php/Certificate_and_Public_Key_Pinning
    DECLARE @sslCert int
    EXEC sp_OAMethod @httpA, 'GetServerSslCert', @sslCert OUT, 'www.ssllabs.com', 443
    EXEC sp_OAGetProperty @httpA, 'LastMethodSuccess', @iTmp0 OUT
    IF @iTmp0 = 0
      BEGIN
        EXEC sp_OAGetProperty @httpA, 'LastErrorText', @sTmp0 OUT
        PRINT @sTmp0
        EXEC @hr = sp_OADestroy @httpA
        RETURN
      END

    -- The GetSpkiFingerprint method returns the SPKI Fingerprint suitable for use in pinning.

    EXEC sp_OAMethod @sslCert, 'GetSpkiFingerprint', @sTmp0 OUT, 'sha256', 'base64'
    PRINT 'SPKI Fingerprint: ' + @sTmp0
    EXEC @hr = sp_OADestroy @sslCert

    -- ------------------------------------------------------------------------------------

    -- At the time of writing this example (on 19-Dec-2015) the sha256/base64 SPKI fingerprint
    -- for the ssllabs.com server certificate is: xkWf9Qfs1uZi2NcMV3Gdnrz1UF4FNAslzApMTwynaMU=

    DECLARE @httpB int
    -- Use "Chilkat_9_5_0.Http" for versions of Chilkat < 10.0.0
    EXEC @hr = sp_OACreate 'Chilkat.Http', @httpB OUT

    -- Set the TlsPinSet.  The format of the TlsPinSet string is:
    --  "hashAlg, encoding, fingerprint1, fingerprint2, ..."
    EXEC sp_OASetProperty @httpB, 'TlsPinSet', 'sha256, base64, xkWf9Qfs1uZi2NcMV3Gdnrz1UF4FNAslzApMTwynaMU='

    -- Our object will refuse to communicate with any TLS server where the server's public key
    -- does not match a pin in the pinset.

    -- This should be OK (assuming the ssllabs.com server certificate has not changed since
    -- the time of writing this example).
    DECLARE @html nvarchar(4000)
    EXEC sp_OAMethod @httpB, 'QuickGetStr', @html OUT, 'https://www.ssllabs.com/'
    EXEC sp_OAGetProperty @httpB, 'LastMethodSuccess', @iTmp0 OUT
    IF @iTmp0 = 0
      BEGIN
        EXEC sp_OAGetProperty @httpB, 'LastErrorText', @sTmp0 OUT
        PRINT @sTmp0
        EXEC @hr = sp_OADestroy @httpA
        EXEC @hr = sp_OADestroy @httpB
        RETURN
      END


    PRINT 'Success.  The HTTP GET worked because the server''s certificate had a matching public key.'

    -- This should NOT be OK because owasp.org's server certificate will not have a matching public key.
    EXEC sp_OAMethod @httpB, 'QuickGetStr', @html OUT, 'https://www.owasp.org/index.php/Certificate_and_Public_Key_Pinning'
    EXEC sp_OAGetProperty @httpB, 'LastMethodSuccess', @iTmp0 OUT
    IF @iTmp0 = 0
      BEGIN

        PRINT 'Good, this connection was rejected...'
      END
    ELSE
      BEGIN

        PRINT 'This was not supposed to happen!'
        EXEC @hr = sp_OADestroy @httpA
        EXEC @hr = sp_OADestroy @httpB
        RETURN
      END

    EXEC @hr = sp_OADestroy @httpA
    EXEC @hr = sp_OADestroy @httpB


END
GO