processing / processing/processing4
Sign exported applications on Windows
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 494
- Forks
- 183
- Avg merge
- 4h 39m
- Merged PRs (30d)
- 3
Description
Created by: benfry
Similar to #25, but specific to the .exe files created when exporting applications on Windows.
(We're already doing this on macOS.)
Possible useful resource for getting started: https://stackoverflow.com/questions/252226/signing-a-windows-exe-file
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is named. Start by tracing the Windows application export path and comparing it with the existing macOS signing flow; use the linked Windows executable-signing resource for background. Done means exported Windows .exe files are signed successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- operating-systems, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100