SQL Server

Code Signing using Sectigo USB Token

See more Code Signing Examples

Demonstrates how to Authenticode sign an EXE or DLL using a SafeNet USB token from Sectigo.

Requires Chilkat v10.0.0 or greater.

SQL Server

-- Important: See this note about string length limitations for strings returned by sp_OAMethod calls.
--
CREATE PROCEDURE ChilkatSample
AS
BEGIN
    DECLARE @hr int
    DECLARE @sTmp0 nvarchar(4000)
    DECLARE @success int
    SELECT @success = 0

    --  This example requires the Chilkat API to have been previously unlocked.
    --  See Global Unlock Sample for sample code.

    --  First create the following JSON to specify that SHA256 is to be used,
    --  and provide timestamp server information.

    --  {
    --    "hashAlg": "sha256",
    --    "timestampToken": {
    --      "enabled": true,
    --      "tsaUrl": "http://timestamp.digicert.com",
    --      "requestTsaCert": true,
    --      "hashAlg": "sha256"
    --    }
    --  }

    DECLARE @json int
    EXEC @hr = sp_OACreate 'Chilkat.JsonObject', @json OUT
    IF @hr <> 0
    BEGIN
        PRINT 'Failed to create ActiveX component'
        RETURN
    END

    EXEC sp_OAMethod @json, 'UpdateString', @success OUT, 'hashAlg', 'sha256'
    EXEC sp_OAMethod @json, 'UpdateBool', @success OUT, 'timestampToken.enabled', 1
    EXEC sp_OAMethod @json, 'UpdateString', @success OUT, 'timestampToken.tsaUrl', 'http://timestamp.digicert.com'
    EXEC sp_OAMethod @json, 'UpdateBool', @success OUT, 'timestampToken.requestTsaCert', 1
    EXEC sp_OAMethod @json, 'UpdateString', @success OUT, 'timestampToken.hashAlg', 'sha256'

    --  The only difference in signing with a smartcard or USB token
    --  is that the cert is loaded from a smartcard or USB token, instead of a PFX or from elsewhere
    --  such as from the Windows certificate store.
    DECLARE @cert int
    EXEC @hr = sp_OACreate 'Chilkat.Cert', @cert OUT

    --  Use your USB token PIN (user password).
    --  It will be a string similar to this:  j6X54nB7-jlp5Cr2
    EXEC sp_OASetProperty @cert, 'SmartCardPin', 'j6X54nB7-jlp5Cr2'

    --  Load the certificate based on the serial number.
    --  *** Use your certificate's serial number.
    EXEC sp_OAMethod @cert, 'LoadFromSmartcard', @success OUT, 'serial=3FF5B69109BFD4046C92CC0D18EE23C2'
    IF @success = 0
      BEGIN
        EXEC sp_OAGetProperty @cert, 'LastErrorText', @sTmp0 OUT
        PRINT @sTmp0
        EXEC @hr = sp_OADestroy @json
        EXEC @hr = sp_OADestroy @cert
        RETURN
      END

    --  Note: If the above fails, then use the SafeNet Authentication Client Tools
    --  to login to your token using your token password.
    --  You don't want too many failed logins, otherwise you'll lock the token.
    --  A successful login will reset number of failed logins back to 0.

    --  Note: This is to sign Microsoft Windows executables or DLLs
    --  You can sign .exe or .dll files.
    DECLARE @exePath nvarchar(4000)
    SELECT @exePath = 'C:/someDirectory/HelloWorld.exe'

    DECLARE @signer int
    EXEC @hr = sp_OACreate 'Chilkat.CodeSign', @signer OUT

    --  If successful, the following call will apply the signature to the EXE (or DLL).
    EXEC sp_OAMethod @signer, 'AddSignature', @success OUT, @exePath, @cert, @json
    IF @success = 0
      BEGIN
        EXEC sp_OAGetProperty @signer, 'LastErrorText', @sTmp0 OUT
        PRINT @sTmp0
        EXEC @hr = sp_OADestroy @json
        EXEC @hr = sp_OADestroy @cert
        EXEC @hr = sp_OADestroy @signer
        RETURN
      END


    PRINT 'Successfully applied the Authenticode signature.'

    EXEC @hr = sp_OADestroy @json
    EXEC @hr = sp_OADestroy @cert
    EXEC @hr = sp_OADestroy @signer


END
GO