Skip to content

Latest commit

Β 

History

4 Commits

Folders and files

NameName
Last commit message
Last commit date
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 

Repository files navigation

πŸ›‘οΈ EXE Signer Tool V2

A Next-Gen, High-Performance GUI Application for Digitally Signing Windows Executable Files & Establishing Zero-Warning Code Trust.

Tauri v2 Rust Vite License Platform


🌟 Key Features

  • ⚑ Ultra Fast & Lightweight: Powered by Tauri v2 and Rust for minimal memory footprint and instant startup.
  • πŸ”‘ RSA-4096 Certificate Generator: Generate custom self-signed code-signing certificates (.pfx) with configurable Organization, Country, Locality, and Expiry up to 100 years.
  • πŸ›‘οΈ One-Click EXE Signing: Seamlessly signs Windows Executables (.exe) with SHA256 signatures and RFC 3161 timestamping using Windows SignTool.
  • πŸ€– Multi-Language Trust Bootstrap Snippets: Automatically generates zero-config trust injection code snippets for 8 programming languages (C++, C#, Node.js, Python, Go, Rust, Batch, PowerShell) so end-users never see Windows SmartScreen / "Unknown Publisher" warnings.
  • 🎯 Auto SDK Detection: Automatically scans and detects installed Windows Kits SDK signtool.exe paths across Windows 10/11 installations.
  • πŸ–₯️ Cockpit Dark UI: Modern dark theme with real-time status telemetry output, path tooltips, and custom window management.

βš™οΈ Prerequisites

Before building or running the project locally, ensure you have:

  1. Windows 10 / 11
  2. Node.js (v18 or higher) & npm
  3. Rust Toolchain: Install via rustup.rs (MSVC toolchain required for Windows)
  4. Windows 10/11 SDK: For signtool.exe (included in Visual Studio C++ Build Tools or standalone Windows SDK)

πŸš€ Getting Started

1. Clone the Repository

git clone https://github.com/MZarc/exe-signer-tool.git
cd exe-signer-tool

2. Install Dependencies

npm install

3. Run in Development Mode

Launch the application with live reload:

npm run tauri dev

4. Build Production Executable

To compile a standalone production release .exe:

npm run tauri build

The compiled binary will be located in src-tauri/target/release/.


πŸ“‚ Project Architecture

exe-signer-tool/
β”œβ”€β”€ public/                 # Static web assets
β”œβ”€β”€ src/                    # Frontend UI (HTML, CSS, JavaScript)
β”‚   β”œβ”€β”€ index.html          # Cockpit GUI layout & components
β”‚   β”œβ”€β”€ main.js             # Event handlers, state management & Tauri IPC
β”‚   β”œβ”€β”€ style.css           # Modern Cyberpunk theme styling
β”‚   └── styles.css          # Base utilities & animations
β”œβ”€β”€ src-tauri/              # Rust Backend (Tauri v2)
β”‚   β”œβ”€β”€ src/                # Rust commands (Certificate gen, SignTool IPC)
β”‚   β”œβ”€β”€ resources/          # Bundled binaries & resources
β”‚   β”œβ”€β”€ Cargo.toml          # Rust dependencies & app configuration
β”‚   └── tauri.conf.json     # Tauri app configuration
β”œβ”€β”€ package.json            # NPM scripts and dependencies
β”œβ”€β”€ vite.config.js          # Vite build configuration
β”œβ”€β”€ LICENSE                 # MIT License
└── README.md               # Project documentation

πŸ”’ Security & Code Signing Notes

  • Self-Signed vs Commercial Certificates: Self-signed certificates are ideal for internal distribution, personal tools, and testing. To eliminate warnings on un-configured third-party client machines without trust bootstrap, purchase an EV/OV certificate from an accredited CA (Sectigo, DigiCert, GlobalSign).
  • Secret Hygiene: Never commit private key .pfx certificate files or passwords to public repositories. .pfx files are automatically ignored by this repository's .gitignore.

πŸ“„ License

Distributed under the MIT License. See LICENSE for details.


Crafted with ❀️ by Meet Mistry

Releases

Contributors

Languages