Add GlobalSign Root CA - R3 cert and remove outdated certs #4100
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
root CA of rubygems.org (and all subdomains) was updated from GlobalSign Organization Validation CA - SHA256 - G2 to GlobalSign Root CA - R3. GlobalSignRootCA.pem was previously used to verify server cert if system certs could not verify rubygems.org cert
hsbt
approved these changes
Dec 7, 2020
|
@sonalkr132 Thanks! I will backport this to RG 2.7, 3.0 and 3.1. |
hsbt
added a commit
that referenced
this pull request
Dec 7, 2020
Add GlobalSign Root CA - R3 cert and remove outdated certs
hsbt
added a commit
that referenced
this pull request
Dec 7, 2020
Add GlobalSign Root CA - R3 cert and remove outdated certs
hsbt
added a commit
that referenced
this pull request
Dec 7, 2020
Add GlobalSign Root CA - R3 cert and remove outdated certs
hsbt
added a commit
that referenced
this pull request
Dec 7, 2020
Add GlobalSign Root CA - R3 cert and remove outdated certs
|
Thanks. Perhaps we should wait until @dwradcliffe confirms the removal of the old cert. |
|
Ah, OK. I'm waiting to release the new versions of rubygems until approval from @dwradcliffe . |
|
I can confirm that we previously used CloudFront as the S3 CDN, and we now use Fastly instead. It is ok to remove |
deivid-rodriguez
pushed a commit
that referenced
this pull request
Dec 7, 2020
Add GlobalSign Root CA - R3 cert and remove outdated certs (cherry picked from commit 9bb7da6)
|
I think there was still a cloudfront domain setup for legacy clients buts it’s probably time to stop supporting that. |
deivid-rodriguez
pushed a commit
that referenced
this pull request
Dec 7, 2020
Add GlobalSign Root CA - R3 cert and remove outdated certs (cherry picked from commit 9bb7da6)
deivid-rodriguez
pushed a commit
that referenced
this pull request
Dec 7, 2020
Add GlobalSign Root CA - R3 cert and remove outdated certs (cherry picked from commit 9bb7da6)
matzbot
pushed a commit
to ruby/ruby
that referenced
this pull request
Dec 9, 2020
Add GlobalSign Root CA. rubygems/rubygems#4100 rubygems/rubygems#4105
64kramsystem
added a commit
to 64kramsystem/ruby-packer-dev
that referenced
this pull request
Feb 17, 2021
The bundled Rubygems certificate `AddTrustExternalCARoot.pem` is outdated; replaced it with the current `GlobalSignRootCA_R3.pem`, from the Rubygems project. See: - rubygems/rubygems#4099 - rubygems/rubygems#4100 - https://github.com/rubygems/rubygems/blob/master/lib/rubygems/ssl_certs/rubygems.org/GlobalSignRootCA_R3.pem
64kramsystem
added a commit
to 64kramsystem/ruby-packer-dev
that referenced
this pull request
Feb 17, 2021
The bundled Rubygems certificate `AddTrustExternalCARoot.pem` is outdated; replaced it with the current `GlobalSignRootCA_R3.pem`, from the Rubygems project. See: - rubygems/rubygems#4099 - rubygems/rubygems#4100 - https://github.com/rubygems/rubygems/blob/master/lib/rubygems/ssl_certs/rubygems.org/GlobalSignRootCA_R3.pem
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
root CA of rubygems.org (and all subdomains) was updated from GlobalSign Organization Validation CA - SHA256 - G2 to GlobalSign Root CA - R3.
GlobalSignRootCA.pem was previously used to verify server cert if system certs could not verify rubygems.org cert.
What was the end-user or developer problem that led to this PR?
Fixes when rubygem.org cert could not be verified by using system certs:
closes: #4099
What is your fix for the problem, implemented in this PR?
add GlobalSign R3 CA cert. used here to configure remove fetcher.
Make sure the following tasks are checked