SQL Server Requires Chilkat v11.7.0+
SQL Server
Authenticode Sign a VBScript File (.vbs)
See more Code Signing Examples
Demonstrates how to Authenticode sign a VBScript file (.vbs). Signing VBScript files requires Chilkat v11.7.0 or later. The signature is appended to the file as a comment block.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 @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 VBScript file (.vbs) 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
-- 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 @scriptPath nvarchar(4000)
SELECT @scriptPath = 'C:/someDir/Backup.vbs'
DECLARE @signer int
EXEC @hr = sp_OACreate 'Chilkat.CodeSign', @signer OUT
-- The script is modified in place. The signature is appended to the end of the file as a comment block:
--
-- '' SIG '' Begin signature block
-- '' SIG '' MIIoKgYJKoZIhvcNAQcCoIIoGzCCKBcCAQExDzANBglg
-- '' SIG '' ...
-- '' SIG '' End signature block
--
-- If the script is already signed, the new signature block replaces the existing one.
EXEC sp_OAMethod @signer, 'AddSignature', @success OUT, @scriptPath, @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 VBScript file.'
-- 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, @scriptPath, @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.'
-- Note: Other script types, such as JScript (.js), are not supported.
-- AddSignature returns false for an unsupported file type and does not modify the file.
EXEC @hr = sp_OADestroy @cert
EXEC @hr = sp_OADestroy @json
EXEC @hr = sp_OADestroy @signer
EXEC @hr = sp_OADestroy @sigInfo
END
GO