SQL Server Requires Chilkat v11.7.0+
SQL Server
Authenticode Sign a Windows Installer Package (MSI)
See more Code Signing Examples
Demonstrates how to Authenticode sign a Windows Installer package (.msi). Signing MSI packages requires Chilkat v11.7.0 or later. The package is signed in place, and the certificate must have an RSA key: Windows does not accept the signature of an MSI that was signed with an ECDSA certificate.Chilkat SQL Server Downloads
-- 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
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.
-- Signing a Windows Installer package (.msi) requires Chilkat v11.7.0 or later.
-- Load the code signing certificate. It must have access to its private key.
DECLARE @cert int
EXEC @hr = sp_OACreate 'Chilkat.Cert', @cert OUT
IF @hr <> 0
BEGIN
PRINT 'Failed to create ActiveX component'
RETURN
END
EXEC sp_OAMethod @cert, 'LoadPfxFile', @success OUT, 'C:/someDir/myCodeSigningCert.pfx', 'pfx password'
IF @success = 0
BEGIN
EXEC sp_OAGetProperty @cert, 'LastErrorText', @sTmp0 OUT
PRINT @sTmp0
EXEC @hr = sp_OADestroy @cert
RETURN
END
-- Use a certificate with an RSA key to sign an MSI.
-- Windows does not accept the signature of an MSI that was signed with an ECDSA certificate
-- (signtool verify and the Digital Signatures tab of the file's properties report it as invalid).
-- This is a limitation of signed MSI files on Windows. It does not apply to EXE, DLL, PowerShell,
-- or VBScript files, which can be signed with either kind of certificate.
EXEC sp_OAMethod @cert, 'IsRsa', @iTmp0 OUT
IF @iTmp0 = 0
BEGIN
PRINT 'Use an RSA code signing certificate to sign an MSI.'
EXEC @hr = sp_OADestroy @cert
RETURN
END
-- Sign with SHA256, and ask a timestamp authority for a timestamp. A timestamp lets the
-- signature continue to validate after the code signing certificate has expired.
--
-- {
-- "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
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'
DECLARE @msiPath nvarchar(4000)
SELECT @msiPath = 'C:/someDir/MyAppSetup.msi'
DECLARE @signer int
EXEC @hr = sp_OACreate 'Chilkat.CodeSign', @signer OUT
-- The .msi is modified in place. The signature is stored in the package's digital signature stream.
-- If the package is already signed, the new signature replaces the existing one.
EXEC sp_OAMethod @signer, 'AddSignature', @success OUT, @msiPath, @cert, @json
IF @success = 0
BEGIN
EXEC sp_OAGetProperty @signer, 'LastErrorText', @sTmp0 OUT
PRINT @sTmp0
EXEC @hr = sp_OADestroy @cert
EXEC @hr = sp_OADestroy @json
EXEC @hr = sp_OADestroy @signer
RETURN
END
PRINT 'Signed the MSI.'
-- Verify the signature that was just added.
DECLARE @sigInfo int
EXEC @hr = sp_OACreate 'Chilkat.JsonObject', @sigInfo OUT
DECLARE @valid int
EXEC sp_OAMethod @signer, 'VerifySignature', @valid OUT, @msiPath, @sigInfo
IF @valid = 0
BEGIN
EXEC sp_OAGetProperty @signer, 'LastErrorText', @sTmp0 OUT
PRINT @sTmp0
EXEC @hr = sp_OADestroy @cert
EXEC @hr = sp_OADestroy @json
EXEC @hr = sp_OADestroy @signer
EXEC @hr = sp_OADestroy @sigInfo
RETURN
END
PRINT 'The signature is valid.'
EXEC @hr = sp_OADestroy @cert
EXEC @hr = sp_OADestroy @json
EXEC @hr = sp_OADestroy @signer
EXEC @hr = sp_OADestroy @sigInfo
END
GO