beeware / beeware/briefcase

Add code signing for Linux release artefacts

Open
#1,269 0 comments 0 reactions 0 assignees View on GitHub
enhancement linux
Dominant language
Python
Stars
3.3k
Forks
549
Avg merge
1d 4h
Merged PRs (30d)
40

Description

### What is the problem or limitation you are having?

Code signing is an option provided by the `briefcase package` command. However, Linux release artefacts don't currently use these options.

### Describe the solution you'd like

`briefcase package linux` should provide options to sign release artefacts.

`briefcase package linux --identity` should provide options to explicitly provide a signing identity.

### Describe alternatives you've considered

Do nothing. Lack of signing doesn't appear to *prevent* any apps from being installed; however, as a policy, some users might require signed artefacts.

### Additional context

It's not clear what is required to make signing work. It's quite probable that completely different approaches will be needed for each system package format, plus AppImage and Flatpak.

Contributor guide

Open the contributing guide

Research direction

Start at the `briefcase package linux` command and trace how its signing options are handled. Compare the requirements for each named Linux release format—system packages, AppImage, and Flatpak—and determine what “done” means for explicit `--identity` support and signed artefacts across them.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux, python
Domain
build-system, cli, release
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.