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

[PECO-1760] Certifi removes GLOBALTRUST root certificate #410

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

jprakash-db
Copy link
Contributor

@jprakash-db jprakash-db commented Jul 8, 2024

Updated the certify version to "2024.7.4"

Dependabot report:

Package Affected versions Patched version
certifi >= 2021.05.30, < 2024.07.04 2024.07.04

Certifi 2024.07.04 removes root certificates from "GLOBALTRUST" from the root store. These are in the process of being removed from Mozilla's trust store.

GLOBALTRUST's root certificates are being removed pursuant to an investigation which identified "long-running and unresolved compliance issues". Conclusions of Mozilla's investigation can be found here.

Copy link
Contributor

@kravets-levko kravets-levko left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jprakash-db Dependency upgrade looks good 👍 But please remove the .idea folder from the PR. Also, what are that two files in src/databricks/sqlalchemy/test/? Are they relevant to this PR?

@kravets-levko kravets-levko changed the title [ PECO - 1760 ] Certifi removes GLOBALTRUST root certificate [PECO-1760] Certifi removes GLOBALTRUST root certificate Jul 8, 2024
@jprakash-db
Copy link
Contributor Author

@kravets-levko Fixed the issues

@@ -27,6 +27,7 @@ sqlalchemy = { version = ">=2.0.21", optional = true }
openpyxl = "^3.0.10"
alembic = { version = "^1.0.11", optional = true }
urllib3 = ">=1.26"
certifi = "2024.7.4"
Copy link
Contributor

@kravets-levko kravets-levko Jul 8, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Okay, so I checked where this dependency come from. It is a transitive dependency of requests package. Also, I checked the requests itself - its latest version also uses old certifi. So I think in this case it's okay to add a consraint to our project and wait for requests upgrade. Two more things to do:

  1. add a comment that once requests updates certifi to the version that will satisfy us - we should roll this change back and upgrae `requests instead
  2. also, instead of pinning the exact version - better relax the constraint a bit (e.g. "^2024.7.4")

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants