mgradwohl / mgradwohl/Coloma

Sign the EXE

Open
#6 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C#
Stars
2
Forks
5
PR merge metrics
No merged PRs in 30d

Description

From Crisping:

Unsigned email tells me to pull a random .exe and run it elevated, and the **code is not signed** either. Hmmm 

Ran it anyway, this is a strong authenticator  but this is training the wrong behavior across the team.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No file, build entry point, or test is named. Start by locating how the project produces its EXE and reviewing the release process for code-signing support. Done means the distributed executable has a verifiable signature and the release instructions identify how it is signed.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
release, security
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.