Cryptographic signed commits and releases

Open
#288 4 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
git, github
Domain
release, security

Research direction

Start by reading the linked GitHub and Debian references to understand signing commits, tags, and release archives. Then inspect the project’s existing commit and release processes to identify what would need to change. The issue is done when users can verify signatures for the requested commits, tags, and release archives.

Written by the indexing model from the issue text.

Description

enhancement

It would be great if there were electronic signatures (OpenPGP/etc)
of all git commits and tags and any zip files or tarballs you release,
so that distributors and users can verify the source code came from authors of this project
and wasn't modified by github or network attackers.

https://mikegerwitz.com/papers/git-horror-story
https://github.com/blog/2144-gpg-signature-verification
https://wiki.debian.org/Creating%20signed%20GitHub%20releases
https://wiki.debian.org/debian/watch#Cryptographic_signature_verification

Dominant language
C
Stars
1.4k
Forks
523
Avg merge
3d 23h
Merged PRs (30d)
14

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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.

More from cisco/libsrtp

All issues in cisco/libsrtp

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.