rustdesk / rustdesk/rustdesk-server-pro
Feature Request: Use user provided code-signing keys for installers
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 317
- Forks
- 119
- PR merge metrics
- No merged PRs in 30d
Description
We have our own code signing system and have our own validated certificate through Azure Artifact Signing and we'd prefer to use these keys instead of Purslane's.
There were some red flags raised that the keys are controlled/registered to a non NA/EU company, but it would be easier if the signing of the executable was a configurable option or able to be integrated into an existing pipeline.
Contributor guide
No contributing guide indexed for this repository
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
Start by reviewing the repository's installer and signing pipeline to find where Purslane-controlled keys are selected; the issue names no files or entry points. Define how Azure Artifact Signing or another user-provided certificate would be configured, and verify that installers use the supplied keys while preserving the existing default behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, shell
- Domain
- devops, release, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100