Skip to content

Conversation

@sahithvibudhi
Copy link
Owner

  • Configure electron-builder with Windows signing options
  • Add GitHub Actions environment variables for certificate handling
  • Enable SHA256 signing with DigiCert timestamp server
  • Sign all DLLs to ensure complete coverage

Fixes #12

Setup Required:

To complete the code signing setup, the following steps are needed:

  1. Obtain a code signing certificate from a trusted Certificate Authority:

    • Option A: Azure Trusted Signing (recommended for US/Canada organizations)
    • Option B: Extended Validation (EV) certificate for immediate trust
    • Option C: Organization Validation (OV) certificate (builds trust over time)
  2. Convert certificate to base64 format: bash # For .pfx or .p12 files base64 -i certificate.pfx -o certificate_base64.txt

  3. Add GitHub repository secrets:

    • Go to Settings → Secrets and variables → Actions
    • Add WIN_CSC_LINK (base64-encoded certificate content)
    • Add WIN_CSC_KEY_PASSWORD (certificate password)
  4. Create a new release to test the signed build

Once configured, Windows Defender should no longer flag VibeTree as malware.

…e positives

- Configure electron-builder with Windows signing options
- Add GitHub Actions environment variables for certificate handling
- Enable SHA256 signing with DigiCert timestamp server
- Sign all DLLs to ensure complete coverage

Fixes #12

## Setup Required:

To complete the code signing setup, the following steps are needed:

1. [ ] Obtain a code signing certificate from a trusted Certificate Authority:
   - Option A: Azure Trusted Signing (recommended for US/Canada organizations)
   - Option B: Extended Validation (EV) certificate for immediate trust
   - Option C: Organization Validation (OV) certificate (builds trust over time)

2. [ ] Convert certificate to base64 format:
   ```bash
   # For .pfx or .p12 files
   base64 -i certificate.pfx -o certificate_base64.txt
   ```

3. [ ] Add GitHub repository secrets:
   - Go to Settings → Secrets and variables → Actions
   - Add WIN_CSC_LINK (base64-encoded certificate content)
   - Add WIN_CSC_KEY_PASSWORD (certificate password)

4. [ ] Create a new release to test the signed build

Once configured, Windows Defender should no longer flag VibeTree as malware.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Windows Defender reporting malware in VibeTree-0.0.1-Setup.exe

2 participants