Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[1.1] release: add runc.keyring file #3838

Merged
merged 8 commits into from
Apr 26, 2023
Merged

[1.1] release: add runc.keyring file #3838

merged 8 commits into from
Apr 26, 2023

Commits on Apr 22, 2023

  1. release: add runc.keyring file and script

    In order to allow any of the maintainers to cut releases for runc,
    create a keyring file that distributions can use to verify that releases
    are signed by one of the maintainers.
    
    The format matches the gpg-offline format used by openSUSE packaging,
    but it can be easily imported with "gpg --import" so any distribution
    should be able to handle this keyring format wtihout issues.
    
    Each key includes the GitHub handle of the associated user. There isn't
    any way for this information to be automatically verified (outside of
    using something like keybase.io) but since all changes of this file need
    to be approved by maintainers this is okay for now.
    
    Signed-off-by: Aleksa Sarai <cyphar@cyphar.com>
    cyphar committed Apr 22, 2023
    Configuration menu
    Copy the full SHA
    bd1d537 View commit details
    Browse the repository at this point in the history
  2. scripts: release: add verification checks for signing keys

    We need to make sure the release is being signed by a key that is
    actually listed as a trusted signing key, and we also need to ask the
    person cutting the release whether the list of trusted keys is
    acceptable.
    
    Also add some verification checks after a release is signed to make sure
    everything was signed with the correct keys.
    
    Signed-off-by: Aleksa Sarai <cyphar@cyphar.com>
    cyphar committed Apr 22, 2023
    Configuration menu
    Copy the full SHA
    853d5e3 View commit details
    Browse the repository at this point in the history
  3. keyring: verify runc.keyring has legitimate maintainer keys

    These checks ensure that all of the keys in the runc.keyring list are
    actually the keys of the specified user and that the users themselves
    are actually maintainers.
    
    Signed-off-by: Aleksa Sarai <cyphar@cyphar.com>
    cyphar committed Apr 22, 2023
    Configuration menu
    Copy the full SHA
    3bdb63b View commit details
    Browse the repository at this point in the history
  4. keyring: add Aleksa's <asarai@suse.com> signing key

    keyid 5F36C6C61B5460124A75F5A69E18AA267DDB8DB4
    
    This is the signing key I have used for all previous runc releases. You
    can also verify that this is the key trusted by openSUSE for all of our
    releases.
    
    Ref: https://keyserver.ubuntu.com/pks/lookup?search=5F36C6C61B5460124A75F5A69E18AA267DDB8DB4&fingerprint=on&op=index
    Ref: https://build.opensuse.org/package/view_file/openSUSE:Factory/runc/runc.keyring?expand=1&rev=54
    Signed-off-by: Aleksa Sarai <asarai@suse.de>
    cyphar committed Apr 22, 2023
    Configuration menu
    Copy the full SHA
    63355bf View commit details
    Browse the repository at this point in the history
  5. keyring: add Aleksa's <cyphar@cyphar.com> signing key

    keyid C9C370B246B09F6DBCFC744C34401015D1D2D386
    
    This is my personal signing key, which I've used to sign the vast
    majority of my commits on GitHub. While I usually sign releases using my
    <asarai@suse.de> signing key, it doesn't hurt to include this key too.
    
    Ref: https://keyserver.ubuntu.com/pks/lookup?search=C9C370B246B09F6DBCFC744C34401015D1D2D386&fingerprint=on&op=index
    Signed-off-by: Aleksa Sarai <cyphar@cyphar.com>
    cyphar committed Apr 22, 2023
    Configuration menu
    Copy the full SHA
    b6f686f View commit details
    Browse the repository at this point in the history
  6. runc.keyring: add Kolyshkin

    Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
    kolyshkin authored and cyphar committed Apr 22, 2023
    Configuration menu
    Copy the full SHA
    6a806d4 View commit details
    Browse the repository at this point in the history

Commits on Apr 25, 2023

  1. scripts: keyring validate: print some more information

    Add a little bit more diagnostic information to "make validate-keyring".
    
    Signed-off-by: Aleksa Sarai <cyphar@cyphar.com>
    cyphar committed Apr 25, 2023
    Configuration menu
    Copy the full SHA
    b0fae8c View commit details
    Browse the repository at this point in the history
  2. runc.keyring: add Akihiro Suda

    Signed-off-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp>
    AkihiroSuda authored and cyphar committed Apr 25, 2023
    Configuration menu
    Copy the full SHA
    c1063b1 View commit details
    Browse the repository at this point in the history