CodeSign Lua Reference Documentation

chilkat.CodeSign

Current Version: 11.7.0

Markdown version of this page for AI tools (v 11.7.0) · all AI docs

Chilkat.CodeSign

Sign, verify, inspect, and remove Authenticode signatures on Windows executables, installers, and scripts.

Chilkat.CodeSign works directly with Authenticode signatures on Windows executable files such as .exe and .dll, and, starting in v11.7.0, on Windows Installer packages (.msi), PowerShell files (.ps1, .psm1, .psd1), and VBScript files (.vbs). It provides functionality for applying a code-signing signature, validating whether a signed executable can be trusted, extracting signature information, retrieving the signer certificate, and removing an existing signature.

Sign executables, installers, and scripts

Apply Authenticode signatures to EXE, DLL, MSI, PowerShell, and VBScript files using a certificate and associated private key.

Validate trust

Check whether a signed executable has a valid signature and whether the signing certificate chain can be trusted.

Inspect signatures

Extract details about the Authenticode signature, including signer information and signature-related metadata.

Retrieve signer certificates

Get the certificate used to sign the executable and inspect it with Chilkat.Cert.

Remove signatures

Remove an existing Authenticode signature from a signed file when an unsigned output file is required.

Diagnostics

Use detailed diagnostic output to troubleshoot signing, certificate, trust-chain, timestamping, or validation problems.

Common pattern: Load or provide a code-signing certificate that has access to its private key, sign the target file, optionally add timestamping if supported by the signing workflow, then verify the resulting signature and inspect diagnostics if validation does not succeed.

Object Creation

local chilkat = require("chilkat")

local code_sign = chilkat.CodeSign.new()
local code_sign = chilkat.CodeSign.new()

Creates the object (chilkat.CodeSign() does the same). Lua's garbage collector frees it when it is no longer referenced; code_sign:dispose() frees it at once, and in Lua 5.4 and later local code_sign <close> = chilkat.CodeSign.new() frees it when the block ends. Calling a method of a disposed object raises an error.

Errors

A method that fails returns nil followed by the error text, as io.open does: local body, err = code_sign:method(...), where err is the object's last_error_text. Wrap the call in assert() to raise an error with that text instead. Methods that answer a question return true or false, numbers are returned as they are (check last_method_success where the description says a value means failure), and property reads and writes never fail for Chilkat reasons.

Misuse raises a Lua error: a wrong argument type or a missing argument (bad argument #1 to ...), an unknown property name, a write to a read-only property, an out-of-range integer, or an object of the wrong class.

Names are Chilkat's in snake_case: QuickGetStr is quick_get_str, LastErrorText is last_error_text. Properties are fields (code_sign.verbose_logging = true) and methods use the colon (code_sign:method(...)). Strings are UTF-8; binary data is a Lua string of bytes. Indexes are 0-based, as in every Chilkat API. Unlocking: call chilkat.unlock_bundle("...") once at startup.

Properties

DebugLogFilePath
-- strVal is a string
local strVal = code_sign.debug_log_file_path
code_sign.debug_log_file_path = strVal

If set to a file path, this property logs the LastErrorText of each Chilkat method or property call to the specified file. This logging helps identify the context and history of Chilkat calls leading up to any crash or hang, aiding in debugging.

Enabling the VerboseLogging property provides more detailed information. This property is mainly used for debugging rare instances where a Chilkat method call causes a hang or crash, which should generally not happen.

Possible causes of hangs include:

  • A timeout property set to 0, indicating an infinite timeout.
  • A hang occurring within an event callback in the application code.
  • An internal bug in the Chilkat code causing the hang.

More Information and Examples
top
HeartbeatMs
-- intVal is an integer
local intVal = code_sign.heartbeat_ms
code_sign.heartbeat_ms = intVal
Introduced in version 9.5.0.98

Specifies the approximate interval, in milliseconds, between AbortCheck event callbacks during supported operations. An event handler can request that the current operation be aborted.

The default is 0, which disables AbortCheck callbacks. Setting a positive value enables periodic callbacks when an operation is sufficiently long-running; methods that finish quickly may complete without generating one.

Callback interval: The interval is a scheduling target rather than a real-time guarantee. Callback timing can vary while waiting for private-key hardware, a timestamp authority, certificate-chain processing, or other operating-system services.

More Information and Examples
top
LastErrorHtml
-- strVal is a string (read-only)
local strVal = code_sign.last_error_html

Provides HTML-formatted information about the last called method or property. If a method call fails or behaves unexpectedly, check this property for details. Note that information is available regardless of the method call's success.

top
LastErrorText
-- strVal is a string (read-only)
local strVal = code_sign.last_error_text

Provides plain text information about the last called method or property. If a method call fails or behaves unexpectedly, check this property for details. Note that information is available regardless of the method call's success.

top
LastErrorXml
-- strVal is a string (read-only)
local strVal = code_sign.last_error_xml

Provides XML-formatted information about the last called method or property. If a method call fails or behaves unexpectedly, check this property for details. Note that information is available regardless of the method call's success.

top
LastMethodSuccess
-- boolVal is a boolean
local boolVal = code_sign.last_method_success
code_sign.last_method_success = boolVal

Indicates the success or failure of the most recent method call: true means success, false means failure. This property remains unchanged by property setters or getters. This method is present to address challenges in checking for null or Nothing returns in certain programming languages. Note: This property does not apply to methods that return integer values or to boolean-returning methods where the boolean does not indicate success or failure.

top
UncommonOptions
-- strVal is a string
local strVal = code_sign.uncommon_options
code_sign.uncommon_options = strVal
Introduced in version 9.5.0.97

Provides a comma-separated list of specialized compatibility or validation options. The default is an empty string, which is appropriate for normal use.

OptionEffect
codesign-allow-expired-certPrevents Authenticode verification from failing solely because the signing certificate is expired.
codesign-allow-cert-paddingStarting in v11.7.0. Prevents verification of an EXE or DLL from failing solely because the PE certificate table fails the strict check (extra data or entries outside the verified signature). The failed check is still reported in LastErrorText. Use only for files known to carry such data, such as some installers that store configuration data in the certificate table.
Use only for an explicit trust policy: Each option relaxes only the one check it names; neither disables the file-integrity, signature, chain, or other validation checks. codesign-allow-expired-cert is not a substitute for timestamping. A signature carrying a valid trusted timestamp should ordinarily remain verifiable after the signing certificate expires without this option.

top
VerboseLogging
-- boolVal is a boolean
local boolVal = code_sign.verbose_logging
code_sign.verbose_logging = boolVal

If set to true, then the contents of LastErrorText (or LastErrorXml, or LastErrorHtml) may contain more verbose information. The default value is false. Verbose logging should only be used for debugging. The potentially large quantity of logged information may adversely affect peformance.

top
Version
-- strVal is a string (read-only)
local strVal = code_sign.version

Version of the component/library, such as "10.1.0"

More Information and Examples
top

Methods

AddSignature
-- path is a string
-- cert is a chilkat.Cert
-- options is a chilkat.JsonObject
-- ok is true, or nil and err on failure
local ok, err = code_sign:add_signature(path, cert, options)
Introduced in version 9.5.0.97

Adds a Microsoft Authenticode signature to the file specified by path. The file is modified in place. cert supplies the code-signing certificate and must provide access to its associated private key. options supplies the signing configuration as JSON.

Starting in v11.7.0, Windows Installer packages, PowerShell files, and VBScript files can be signed in addition to Windows executables and DLLs. The supported file types are:

File typeExtensionsWhere the signature is stored
Windows PE images.exe, .dll, and other PE files such as .sys and .ocxThe PE certificate table. PE files are identified from the file content, not the extension.
Windows Installer packages (starting in v11.7.0).msiThe package's digital signature stream.
PowerShell scripts, modules, and data files (starting in v11.7.0).ps1, .psm1, .psd1A comment block appended to the file (# SIG # Begin signature block ... # SIG # End signature block). The file's text encoding (UTF-8, UTF-8 with BOM, or UTF-16) is kept.
VBScript files (starting in v11.7.0).vbsA comment block appended to the file ('' SIG '' Begin signature block ... '' SIG '' End signature block).

Any other file type (for example .js, .cab, or .cat) causes the method to return false, with LastErrorText explaining that the file type is not supported, and the file is not modified. The file must already exist; this method does not create it.

Starting in v11.7.0, if the file is already Authenticode-signed, the existing signature is removed and replaced by the new one. (Before v11.7.0, signing an already-signed EXE or DLL added a second signature entry instead of replacing the first.)

MSI packages and ECDSA certificates: Windows does not accept an Authenticode signature on an MSI package when the signing certificate uses an ECDSA key. Windows signature checks, such as signtool verify, Get-AuthenticodeSignature, and the file's Digital Signatures properties, report the signature as invalid (TRUST_E_BAD_DIGEST, 0x80096010). This is a limitation of signed MSI files on Windows, not a Chilkat defect: an MSI signed by Microsoft's signtool with the same ECDSA certificate is rejected in the same way, and its signed content is identical to the signature Chilkat produces. Use an RSA code-signing certificate to sign MSI packages. ECDSA certificates work for EXE, DLL, PowerShell, and VBScript files.

Common options options include:

JSON memberPurpose
hashAlgSelects the file-digest algorithm, such as sha256.
timestampToken.enabledEnables an RFC 3161 timestamp token.
timestampToken.tsaUrlSpecifies the timestamp authority URL.
timestampToken.requestTsaCertRequests inclusion of the timestamp authority certificate.
timestampToken.hashAlgSelects the timestamp-request digest algorithm, such as sha256.
{
  "hashAlg": "sha256",
  "timestampToken": {
    "enabled": true,
    "tsaUrl": "http://timestamp.example.com",
    "requestTsaCert": true,
    "hashAlg": "sha256"
  }
}
Timestamping is strongly recommended: A trusted timestamp records that the signature existed while the code-signing certificate was valid. This normally allows the signature to continue validating after the signing certificate expires, provided the timestamp and certificate chains remain valid under the verifier's trust policy.

Returns true on success, nil, err on failure. The second return value, err, is the object's last_error_text; wrap the call in assert() to raise an error instead.

More Information and Examples
top
GetSignerCert
-- cert is a chilkat.Cert
-- ok is true, or nil and err on failure
local ok, err = code_sign:get_signer_cert(cert)
Introduced in version 10.0.1

Retrieves the X.509 signer certificate discovered by the most recent call to VerifySignature on this CodeSign object. If the certificate is fully available, cert is loaded with it and the method returns true. Otherwise, the method returns false.

The returned object contains the public certificate only; it does not provide the signer's private key. Call this method after VerifySignature and use the same CodeSign instance.

Starting in v11.7.0, the signer certificate is available only after a call to VerifySignature that returned true. After a failed verification, this method returns false.

Certificate retrieval versus trust: Successfully retrieving the signer certificate does not independently validate the signature or establish trust. Use the result of VerifySignature and the returned signature information when making a trust decision.

Returns true on success, nil, err on failure. The second return value, err, is the object's last_error_text; wrap the call in assert() to raise an error instead.

top
RemoveSignature
-- path is a string
-- ok is true, or nil and err on failure
local ok, err = code_sign:remove_signature(path)
Introduced in version 9.5.0.97

Removes the embedded Authenticode signature from the file specified by path: a Windows executable or DLL, or, starting in v11.7.0, a Windows Installer package (.msi), PowerShell file (.ps1, .psm1, .psd1), or VBScript file (.vbs). The file is modified in place. Returns true if the signature is successfully removed; otherwise returns false.

For PowerShell and VBScript files, the signature comment block is removed from the end of the file. For MSI packages, the digital signature stream and the extended signature stream (MsiDigitalSignatureEx) are removed.

Effect of removal: The resulting file is no longer Authenticode-signed and no longer carries the removed publisher and timestamp information. This operation does not delete the signing certificate from a Windows certificate store or alter the private key. Keep a backup when the original signed file must be retained.

Returns true on success, nil, err on failure. The second return value, err, is the object's last_error_text; wrap the call in assert() to raise an error instead.

top
VerifySignature
-- path is a string
-- sig_info is a chilkat.JsonObject
-- ok is true, or nil and err on failure
local ok, err = code_sign:verify_signature(path, sig_info)
Introduced in version 9.5.0.97

Verifies the embedded Microsoft Authenticode signature of the file specified by path: a Windows executable or DLL, or, starting in v11.7.0, a Windows Installer package (.msi), PowerShell file (.ps1, .psm1, .psd1), or VBScript file (.vbs). See AddSignature for the supported file types. Other file types cause the method to return false. Structured information about the signature, signer, certificate chain, digest algorithms, timestamp, and validation result is written to sig_info.

Returns true when the signature satisfies the applicable Authenticode validation checks under the current Windows trust configuration. This includes confirming that the signed portions of the file have not changed and evaluating the signing certificate and timestamp information, as applicable. An unsigned file or a signature that does not validate causes the method to return false. Inspect sig_info and LastErrorText for details.

Starting in v11.7.0, verification of an EXE or DLL also includes a strict check of the PE certificate table: it must hold exactly one signature entry, containing exactly the signature that was verified, with no extra data. Data in the certificate table is not covered by the Authenticode signature (see CVE-2013-3900), so anything hidden there would be unsigned. A file that fails this check causes the method to return false unless the codesign-allow-cert-padding option is set in UncommonOptions.

MSI packages signed with an ECDSA certificate: this method can return true for such a package, while Windows itself reports the signature as invalid. This is a limitation of signed MSI files on Windows, not a Chilkat defect; see the note in AddSignature.

What successful verification means: Authenticode verifies publisher identity, file integrity, and certificate trust according to the validation policy. It does not prove that the software is bug-free, safe to execute, or free of malicious behavior. Trust results can also depend on the Windows trusted-root store, certificate-chain availability, timestamp validity, revocation policy, and other system trust settings.

Returns true on success, nil, err on failure. The second return value, err, is the object's last_error_text; wrap the call in assert() to raise an error instead.

More Information and Examples
top

Events

All Chilkat methods are synchronous: the call returns when the work is done. During a long-running call, chilkat.CodeSign reports progress to the functions given to set_event_handler, in a table keyed by event name (plain functions, not methods: closures carry whatever state they need):

code_sign:set_event_handler({
    percent_done  = function(pct) print(pct .. "%") end,              -- return true to abort
    progress_info = function(name, value) print(name, value) end,
})
code_sign.heartbeat_ms = 250   -- abort_check is called 4 times per second
code_sign:set_event_handler({ event_name = function(...) ... end, ... })

Installs the handlers, replacing any installed before; code_sign:set_event_handler(nil) removes them. The event names are checked when the table is installed: a misspelled one raises an error.

The abort_check handler is called at the interval set by the heartbeat_ms property (0, the default, disables it); percent_done is called when an operation's completion percentage is known; progress_info delivers named progress values. A true return from abort_check or percent_done aborts the running method, which then fails in the usual way (nil, err). An error raised in a handler aborts the method and is raised again from the method call; the object remains usable.

AbortCheck
-- handler: function() ... return abort end -- a true return aborts the method in progress
code_sign:set_event_handler({ abort_check = function() ... end })

Enables a method call to be aborted by triggering the AbortCheck event at intervals defined by the HeartbeatMs property. If HeartbeatMs is set to its default value of 0, no events will occur. For instance, set HeartbeatMs to 200 to trigger 5 AbortCheck events per second.

More Information and Examples

Example

local deadline = os.time() + 30                  -- give up after 30 seconds
code_sign.heartbeat_ms = 250                      -- call the handler 4 times per second
code_sign:set_event_handler({ abort_check = function() return os.time() > deadline end })
top
PercentDone
-- handler: function(pct_done) ... return abort end -- a true return aborts
code_sign:set_event_handler({ percent_done = function(pct_done) ... end })

This provides the percentage completion for any method involving network communications or time-consuming processing, assuming the progress can be measured as a percentage. This event is triggered only when it's possible and logical to express the operation's progress as a percentage. The pctDone argument will range from 1 to 100. For methods that finish quickly, the number of PercentDone callbacks may vary, but the final callback will have pctDone equal to 100. For longer operations, callbacks will not exceed one per percentage point (e.g., 1, 2, 3, ..., 98, 99, 100).

The PercentDone callback also acts as an AbortCheck event. For fast methods where PercentDone fires, an AbortCheck event may not trigger since the PercentDone callback already provides an opportunity to abort. For longer operations, where time between PercentDone callbacks is extended, AbortCheck callbacks enable more responsive operation termination.

To abort the operation, set the abort output argument to true. This will cause the method to terminate and return a failure status or corresponding failure value.

More Information and Examples

Example

code_sign:set_event_handler({
    percent_done = function(pct_done)     -- 0 to 100
        print("Percent done: " .. pct_done)
        return false                       -- return true to abort the method in progress
    end,
})
top
ProgressInfo
-- handler: function(name, value) ... end
code_sign:set_event_handler({ progress_info = function(name, value) ... end })

This event callback provides tag name/value pairs that detail what occurs during a method call. To discover existing tag names, create code to handle the event, emit the pairs, and review them. Most tag names are self-explanatory.

Note: Some Chilkat methods don't fire any ProgressInfo events.

More Information and Examples

Example

code_sign:set_event_handler({
    progress_info = function(name, value) print(name .. ": " .. value) end,
})
top