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
doc/fingerprints.txt: Add the OpenSSL OMC PGP key fingerprint #21015
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We want to move to using this key for tarball and announcement signatures. It won't happen immediately, though, as we must have it specified in the latest update of each release branch, so people can verify properly.
levitte
added
branch: master
Merge to master branch
branch: 1.0.2
Merge to OpenSSL_1_0_2-stable branch
approval: review pending
This pull request needs review by a committer
branch: 1.1.1
Merge to OpenSSL_1_1_1-stable branch
approval: otc review pending
This pull request needs review by an OTC member
branch: 3.0
Merge to openssl-3.0 branch
branch: 3.1
Merge to openssl-3.1
tests: exempted
The PR is exempt from requirements for testing
labels
May 22, 2023
paulidale
approved these changes
May 22, 2023
paulidale
removed
the
approval: otc review pending
This pull request needs review by an OTC member
label
May 22, 2023
The sslapi test failure is curious. But clearly nothing to do with this PR! |
mattcaswell
approved these changes
May 22, 2023
mattcaswell
added
approval: done
This pull request has the required number of approvals
and removed
approval: review pending
This pull request needs review by a committer
labels
May 22, 2023
t8m
approved these changes
May 23, 2023
openssl-machine
added
approval: ready to merge
The 24 hour grace period has passed, ready to merge
and removed
approval: done
This pull request has the required number of approvals
labels
May 23, 2023
This pull request is ready to merge |
openssl-machine
pushed a commit
that referenced
this pull request
May 23, 2023
We want to move to using this key for tarball and announcement signatures. It won't happen immediately, though, as we must have it specified in the latest update of each release branch, so people can verify properly. Reviewed-by: Matt Caswell <matt@openssl.org> Reviewed-by: Paul Dale <pauli@openssl.org> Reviewed-by: Tomas Mraz <tomas@openssl.org> (Merged from #21015)
openssl-machine
pushed a commit
that referenced
this pull request
May 23, 2023
We want to move to using this key for tarball and announcement signatures. It won't happen immediately, though, as we must have it specified in the latest update of each release branch, so people can verify properly. Reviewed-by: Matt Caswell <matt@openssl.org> Reviewed-by: Paul Dale <pauli@openssl.org> Reviewed-by: Tomas Mraz <tomas@openssl.org> (Merged from #21015) (cherry picked from commit f925bfe)
openssl-machine
pushed a commit
that referenced
this pull request
May 23, 2023
We want to move to using this key for tarball and announcement signatures. It won't happen immediately, though, as we must have it specified in the latest update of each release branch, so people can verify properly. Reviewed-by: Matt Caswell <matt@openssl.org> Reviewed-by: Paul Dale <pauli@openssl.org> Reviewed-by: Tomas Mraz <tomas@openssl.org> (Merged from #21015) (cherry picked from commit f925bfe)
Merged to master, 3.1, and 3.0 branches. Thank you. The PR for 1.1.1 and 1.0.2 needs to be slightly different. I'll create it. |
MrE-Fog
pushed a commit
to MrE-Fog/opensslxxixx
that referenced
this pull request
Jun 4, 2023
We want to move to using this key for tarball and announcement signatures. It won't happen immediately, though, as we must have it specified in the latest update of each release branch, so people can verify properly. Reviewed-by: Matt Caswell <matt@openssl.org> Reviewed-by: Paul Dale <pauli@openssl.org> Reviewed-by: Tomas Mraz <tomas@openssl.org> (Merged from openssl/openssl#21015)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
approval: ready to merge
The 24 hour grace period has passed, ready to merge
branch: master
Merge to master branch
branch: 1.0.2
Merge to OpenSSL_1_0_2-stable branch
branch: 1.1.1
Merge to OpenSSL_1_1_1-stable branch
branch: 3.0
Merge to openssl-3.0 branch
branch: 3.1
Merge to openssl-3.1
tests: exempted
The PR is exempt from requirements for testing
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We want to move to using this key for tarball and announcement signatures.
It won't happen immediately, though, as we must have it specified in the
latest update of each release branch, so people can verify properly.