What platforms and software does sslTrus remote code signing support?
The sslTrus remote code signing service is designed to seamlessly integrate with your existing technology stack, offering broad and deep compatibility across platforms and software types to ensure you can complete code signing easily and securely regardless of your development environment.
Deeply integrated development and DevOps platforms
Through APIs and dedicated plugins, our service deeply integrates with mainstream automation toolchains in the industry, enabling "zero-friction" embedding of the signing workflow.
| Category | Specific tools/platforms |
|---|---|
| CI/CD platforms | Jenkins, GitLab CI/CD, GitHub Actions, Azure DevOps, CircleCI, Travis CI |
| Build tools | Maven, Gradle, Apache Ant, MSBuild, Make |
| Scripting and automation | Can be integrated via command line tools, RESTful API with any script that supports HTTP calls (such as Python, Shell, PowerShell) |
Comprehensively covered software and file types
The service supports digital signing for major operating system platforms, development frameworks, and emerging technology artifacts to ensure trust throughout the entire software lifecycle.
| Platform/Type | Supported specific formats and descriptions |
|---|---|
| Microsoft Windows | Authenticode signing: .exe, .dll, .ocx, .sys (driver), .msi, .msix, .appx, .cabKernel-mode code signing: .sys, .cat (for drivers) |
| Apple macOS / iOS | Apple Code Signing: .app, .pkg, .dmg, .xip, .framework, .kext (kernel extensions) Note: To sign macOS/iOS applications, you must use a dedicated certificate issued by a root certificate trusted by Apple. |
| Java Applications | JAR File Signing: Standard .jar file used to verify the integrity of JAR files and the identity of their publisher. |
| Development Frameworks and Plugins | - Microsoft Office: VBA macro project signing - Mozilla: Firefox browser extensions ( .xpi)- Adobe: AIR applications |
| Other and emerging formats | - Containers and cloud-native: Docker images (signing of image manifests) - IoT and embedded: Firmware files ( .bin, .hex, etc.)- Scripts and configuration files: PowerShell scripts ( .ps1), system configuration files, etc.- Open-source packages: Package formats for some mainstream package managers |
Why is compatibility so important?
- Reduce integration costs: There is no need to modify or restructure your existing build and release processes for signing.
- Protect technology investments: Whether you use classic enterprise-grade tools or the latest cloud-native technology stacks, your signing needs can be met.
- Adapt to future development: Support for formats such as Docker and firmware ensures that your software supply chain security strategy can cover all levels from applications to infrastructure.