CodeSign Secure Documentation
  • Overview
    • About CodeSign Secure
    • Getting Started
    • Documentation Guide
    • Portal Overview
    • Troubleshooting
      • FAQ
    • Glossary
  • Reference Guide
    • Header Bar
      • CodeSign Secure Documentation
      • Swagger API
      • Profile Section
    • Dashboard
      • Key Performance Indicators
      • Issued Certificates
      • Signatures Generated
      • HSM Health Check
    • Keys and Certificates
      • Key and Certificate Lifecycle
    • App Management
    • Signing Requests
      • Approval Workflows
    • Signing Tools
    • Reports
      • Signing Request Report
      • Audit Trail
      • Certificate Report
      • Client Report
    • Logs
    • System Setup
      • Identity Store
      • Backup
      • User
      • Roles and Permissions
      • Email
      • Signing Projects
      • SSL/TLS Management
      • Environment
      • Plugins
  • Setup & Architecture
    • Identity and Access Control
    • Architecture and Concepts
    • Installation
      • Windows
        • Installing the Server
        • Ports and Protocols
        • High Availability and Backup
        • Upgrades and Compatibility
    • Security
      • Security Hardening Checklist
      • Client Authentication
      • Designing Signing Policies
  • Release Notes
    • Releases for 2026
      • v3.2.1
    • Releases for 2025
      • v3.2.0
    • Releases for 2024
      • v3.1.0
  • API Reference
    • Getting Started
    • Authorizing Requests
    • Securing API Access
    • Request and Response Conventions
    • Endpoint Reference
      • Signing
      • Signing Requests
      • Certificates
      • Applications and Environments
      • User Management
      • Permissions
      • Email
      • System Setup
      • Reports
      • Dashboard
      • License
  • Integration Guides
    • Signing Capabilities
      • Supported Formats and Platforms
      • Timestamping
      • Windows Signing - SignTool
        • Signing
        • Macro Signing
      • Apple Signing
      • AppX & MSIX Signing
      • Visual Studio ClickOnce
      • Jar Signing
      • Sign HLK/HCK using CodeSign Secure
      • NuGet Signing
      • Mage Signing
      • Sign OVA/OVF using Encryption Consulting’s Utility Tool
      • Utility Tool for code signing
      • Container Signing
      • PKCS11 Wrapper
        • APK Signing
        • OpenSSL Signing
        • XML Signing
        • JSign Tool Signing
        • Jarsigner Signing
        • GPG2, Debian & RPM Signing
      • Reproducible Build
        • Automated Hash Validation
        • Reproducible Build Process Flow
        • Pipeline Script Components
        • Hash Validation
    • CI/CD Integration
      • GitHub Actions
      • Jenkins
      • GitLab
      • Azure DevOps
      • TeamCity
      • Bamboo
      • Securing CI/CD Credentials

Utility Tool for code signing

The following tool will help you perform code signing through the command line. The tool supports single signing and bulk signing. For single signing, it will take the path of your file as an input, and when performing bulk signing, it will take the path of the folder which contains all the files that need to be signed. It will then automatically scan it for virus, and if malware is detected, the process exits and does not allow signing to continue when single signing.

In bulk signing, it will skip that file. Once the file has been scanned for malware, as per the file type, an appropriate code signing method will be selected for you. For example, files with the .so and .txt extension will be signed with OpenSSL, files with the .jar extension will be signed with Jar signing, and files with the .exe, .dll, .sys, .cat, .cab will be signed with windows signing.

Installation of Utility Tool

For installation, you would need to download and run a MSI file from the portal which will install this tool into your machine. Along with the tool, it will also prompt you to install various signing softwares such as Windows SDK, Java SDK and Encryption Consulting KSP. These signing softwares will be used by the Utility Tool to perform signing operation on different file types.

After successful installation, you will find the Utility Tool.exe in the "C:\Program Files\Encryption Consulting\Utility Tool" directory.

You will need to change the "BASEURL" field in the config file with the URL of your domain

Utility Tool Path

You can cancel the installation of signing softwares if updated versions are already configured in your system environment.

Single Signing

Follow the steps below to use the tool for single file signing:

  1. To Access the tool, click on the executable file- Utility Tool.exe

    Utility Tool Executable

  2. It will prompt you to provide your username, Application Name and Environment Name that will perform user authentication on the portal and verify the user's team details.

    Utility Tool Authentication

  3. It will then ask you whether you want to bulk sign or not, Y for Yes and N for No. Enter N in this case.

    Utility Tool Single Signing

  4. Then enter the path of the file that needed to be signed.

    Utility Tool File Path

  5. Once you provide the file path, malware check is done if ClamAV antivirus software is present in your system. Provide the inputs as asked. An example of doing .exe file with Windows signing is provided below.

    Utility Tool inputs

  6. A message will be displayed when Codesigning is done.

    Utility Tool Single File Signing

All possible inputs that users may have to provide for code signing are listed below with an example of each.

  • Enter the path of the file

    This is where you provide the path of file that you want to sign. Example C:\<Folder_name>\<File_name>. Make sure you have provided a file name with the proper extension.

  • Enter the key name

    This refers to the cryptographic key used to sign the code. Example: evcodesigning

  • Enter the certificate location

    An example of what can be put in this field is C:\testing.pem. The certificate.pem file MUST be included in this input.

  • Enter Hashing Algorithm

    You need provide the name of hashing algorithm such as SHA256, SHA384, or SHA512. It must be one of these three values.

Bulk Signing

Follow the steps below to use the tool for bulk file signing:

  1. To Access the tool, click on the executable file- UtilityTool.exe. This file will be located at

    C:\Program Files (x86)\Encryption Consulting\Utility Tool\UtilityTool.exe

    Utility Tool Executable

  2. It will prompt you to provide your username, Application Name and Environment Name that will perform user authentication on the portal and verify the user's team details.

    Utility Tool Authentication

  3. It will then ask you whether you want to bulk sign or not, Y for Yes and N for No. Enter Y in this case.

    Utility Tool Bulk Signing

  4. Then enter the path of the folder which contains all the files that needed to be signed.

    Utility Tool Folder Path

  5. Now, provide the key name of the certificate which you want to use for signing. Key name or key alias can be seen from the portal.

    Utility Tool Certificate Key Alias

  6. Now, provide the path of this certificate that will be used for signing the file.

    Utility Tool Certificate Path

  7. Then enter the url of the timestamping server. Press enter to select the default server i.e. http://timestamp.digicert.com

    Utility Tool Timestamping Server

  8. Then enter the hashing algorithm (Accepted algorithm: SHA256, SHA384, SHA512)

    Utility Tool Hashing Algorith

  9. It will then generate a Signing Report for all files. It will provide details about successful signings, failed signing and skipped files.

    Signing Report

On this Page:
Support Privacy Policy Terms of Service

Copyright Encryption Consulting LLC. All rights reserved.