2.1 KiB
| stage | group | info |
|---|---|---|
| Enablement | Distribution | To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments |
Package Signatures (FREE SELF)
As of the release of GitLab 9.5 on August 22, 2017, GitLab provides signed Omnibus GitLab packages for RPM and DEB based distributions. This means that all packages provided on https://packages.gitlab.com are signed, starting with 9.5.0, and all future versions of supported branches (for example 9.3.x and 9.4.x after August 22, 2017). Any package version prior to August 22, 2017, will not be signed. Please pass the appropriate argument to your package manager. (Example: yum --nogpgcheck)
Omnibus GitLab packages produced by GitLab are created via the Omnibus tool, for which GitLab has added DEB signing via debsigs in our own fork. This addition, combined with the existing functionality of RPM signing, allows GitLab to provide signed packages for all supported distributions using DEB or RPM.
These packages are produced by the GitLab CI process, as found in the Omnibus GitLab project, prior to their delivery to https://packages.gitlab.com to ensure provide assurance that the packages are not altered prior to delivery to our community.
GnuPG Public Keys
All packages are signed with GnuPG, in a method appropriate for their format. The key used to sign these packages can be found on pgp.mit.edu at 0x3cfcf9baf27eab47
Verifying Signatures
Information on how to verify GitLab package signatures can be found in Package Signatures.
GPG Signature Management
Information on how GitLab manages GPG keys for package signing can be found in the runbooks.