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

build(deps): bump cryptography from 2.9 to 3.2 in /tests #2898

Closed

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Oct 27, 2020

Bumps cryptography from 2.9 to 3.2.

Changelog

Sourced from cryptography's changelog.

3.2 - 2020-10-25


* **SECURITY ISSUE:** Attempted to make RSA PKCS#1v1.5 decryption more constant
  time, to protect against Bleichenbacher vulnerabilities. Due to limitations
  imposed by our API, we cannot completely mitigate this vulnerability and a
  future release will contain a new API which is designed to be resilient to
  these for contexts where it is required. Credit to **Hubert Kario** for
  reporting the issue. *CVE-2020-25659*
* Support for OpenSSL 1.0.2 has been removed. Users on older version of OpenSSL
  will need to upgrade.
* Added basic support for PKCS7 signing (including SMIME) via
  :class:`~cryptography.hazmat.primitives.serialization.pkcs7.PKCS7SignatureBuilder`.

.. _v3-1-1:

3.1.1 - 2020-09-22

  • Updated Windows, macOS, and manylinux wheels to be compiled with OpenSSL 1.1.1h.

.. _v3-1:

3.1 - 2020-08-26


* **BACKWARDS INCOMPATIBLE:** Removed support for ``idna`` based
  :term:`U-label` parsing in various X.509 classes. This support was originally
  deprecated in version 2.1 and moved to an extra in 2.5.
* Deprecated OpenSSL 1.0.2 support. OpenSSL 1.0.2 is no longer supported by
  the OpenSSL project. The next version of ``cryptography`` will drop support
  for it.
* Deprecated support for Python 3.5. This version sees very little use and will
  be removed in the next release.
* ``backend`` arguments to functions are no longer required and the
  default backend will automatically be selected if no ``backend`` is provided.
* Added initial support for parsing certificates from PKCS7 files with
  :func:`~cryptography.hazmat.primitives.serialization.pkcs7.load_pem_pkcs7_certificates`
  and
  :func:`~cryptography.hazmat.primitives.serialization.pkcs7.load_der_pkcs7_certificates`
  .
* Calling ``update`` or ``update_into`` on
  :class:`~cryptography.hazmat.primitives.ciphers.CipherContext` with ``data``
  longer than 2\ :sup:`31` bytes no longer raises an ``OverflowError``. This
  also resolves the same issue in :doc:`/fernet`.

.. _v3-0:

3.0 - 2020-07-20 </tr></table>

... (truncated)

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

@dependabot dependabot bot requested a review from a team as a code owner October 27, 2020 21:16
@bert-e
Copy link
Contributor

bert-e commented Oct 27, 2020

Hello dependabot[bot],

My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.

Status report is not available.

@dependabot dependabot bot added kind:dependencies Pull requests that update a dependency file python Pull requests that update Python code labels Oct 27, 2020
@bert-e
Copy link
Contributor

bert-e commented Oct 27, 2020

Integration data created

I have created the integration data for the additional destination branches.

The following branches will NOT be impacted:

  • development/1.0
  • development/1.1
  • development/1.2
  • development/1.3
  • development/2.0
  • development/2.1
  • development/2.2
  • development/2.3
  • development/2.4
  • development/2.5

You can set option create_pull_requests if you need me to create
integration pull requests in addition to integration branches, with:

@bert-e create_pull_requests

@bert-e
Copy link
Contributor

bert-e commented Oct 27, 2020

Waiting for approval

The following approvals are needed before I can proceed with the merge:

  • the author

  • one peer

Peer approvals must include at least 1 approval from the following list:

@dependabot dependabot bot changed the base branch from development/2.6 to development/2.7 November 25, 2020 09:59
@bert-e
Copy link
Contributor

bert-e commented Nov 25, 2020

Branches have diverged

This pull request's source branch dependabot/pip/tests/cryptography-3.2 has diverged from
development/2.7 by more than 50 commits.

To avoid any integration risks, please re-synchronize them using one of the
following solutions:

  • Merge origin/development/2.7 into dependabot/pip/tests/cryptography-3.2
  • Rebase dependabot/pip/tests/cryptography-3.2 onto origin/development/2.7

Note: If you choose to rebase, you may have to ask me to rebuild
integration branches using the reset command.

@gdemonet
Copy link
Contributor

@dependabot rebase

@dependabot dependabot bot force-pushed the dependabot/pip/tests/cryptography-3.2 branch from 04a2123 to 66bd5b9 Compare November 25, 2020 10:08
@bert-e
Copy link
Contributor

bert-e commented Nov 25, 2020

Waiting for approval

The following approvals are needed before I can proceed with the merge:

  • the author

  • one peer

Peer approvals must include at least 1 approval from the following list:

gdemonet
gdemonet previously approved these changes Nov 25, 2020
@bert-e
Copy link
Contributor

bert-e commented Dec 9, 2020

Branches have diverged

This pull request's source branch dependabot/pip/tests/cryptography-3.2 has diverged from
development/2.7 by more than 50 commits.

To avoid any integration risks, please re-synchronize them using one of the
following solutions:

  • Merge origin/development/2.7 into dependabot/pip/tests/cryptography-3.2
  • Rebase dependabot/pip/tests/cryptography-3.2 onto origin/development/2.7

Note: If you choose to rebase, you may have to ask me to rebuild
integration branches using the reset command.

@NicolasT
Copy link
Contributor

NicolasT commented Dec 9, 2020

@dependabot rebase

@bert-e
Copy link
Contributor

bert-e commented Dec 9, 2020

Waiting for approval

The following approvals are needed before I can proceed with the merge:

  • the author

  • one peer

Peer approvals must include at least 1 approval from the following list:

NicolasT
NicolasT previously approved these changes Dec 9, 2020
@NicolasT
Copy link
Contributor

@dependabot rebase

NicolasT added a commit that referenced this pull request Dec 16, 2020
NicolasT added a commit that referenced this pull request Dec 16, 2020
Ran `tox -e pip-compile` to bring everything up-to-date.

Closes: #2897
Closes: #2898
NicolasT added a commit that referenced this pull request Dec 17, 2020
Due to changes in `pluggy` (a dependency of `pytest`) using the
`importlib.metadata` module from the standard library instead of the
`importlib-metadata` package when running on Python >= 3.8, we need to
pin the `basepython` used in the `pip-compile` Tox env to the version
that's actually used in CI, otherwise `pip` complains during
installation of dependencies the `importlib-metadata` package is not
listed (with hashes) in some `requirements.txt`. As such, setting
`basepython` to `python3.6`, similar to 8a9104b.

Also, update the versions of `pip` and `pip-tools` used in the
`pip-compile` `tox` target, and use the `--allow-unsafe` flag which is
supposedly not really unsafe at all (and will become the default).

See: 8a9104b
Closes: #2897
Closes: #2898
See: pytest-dev/pluggy#222
See: https://github.com/pytest-dev/pluggy/pull/223/files#diff-60f61ab7a8d1910d86d9fda2261620314edcae5894d5aaa236b821c7256badd7
See: jazzband/pip-tools#806 (comment)
NicolasT added a commit that referenced this pull request Dec 17, 2020
Due to changes in `pluggy` (a dependency of `pytest`) using the
`importlib.metadata` module from the standard library instead of the
`importlib-metadata` package when running on Python >= 3.8, we need to
pin the `basepython` used in the `pip-compile` Tox env to the version
that's actually used in CI, otherwise `pip` complains during
installation of dependencies the `importlib-metadata` package is not
listed (with hashes) in some `requirements.txt`. As such, setting
`basepython` to `python3.6`, similar to 8a9104b.

Also, update the versions of `pip` and `pip-tools` used in the
`pip-compile` `tox` target, and use the `--allow-unsafe` flag which is
supposedly not really unsafe at all (and will become the default).

See: 8a9104b
Closes: #2897
Closes: #2898
See: pytest-dev/pluggy#222
See: https://github.com/pytest-dev/pluggy/pull/223/files#diff-60f61ab7a8d1910d86d9fda2261620314edcae5894d5aaa236b821c7256badd7
See: jazzband/pip-tools#806 (comment)
NicolasT added a commit that referenced this pull request Dec 17, 2020
Due to changes in `pluggy` (a dependency of `pytest`) using the
`importlib.metadata` module from the standard library instead of the
`importlib-metadata` package when running on Python >= 3.8, we need to
pin the `basepython` used in the `pip-compile` Tox env to the version
that's actually used in CI, otherwise `pip` complains during
installation of dependencies the `importlib-metadata` package is not
listed (with hashes) in some `requirements.txt`. As such, setting
`basepython` to `python3.6`, similar to 8a9104b.

Also, update the versions of `pip` and `pip-tools` used in the
`pip-compile` `tox` target, and use the `--allow-unsafe` flag which is
supposedly not really unsafe at all (and will become the default).

See: 8a9104b
Closes: #2897
Closes: #2898
See: pytest-dev/pluggy#222
See: https://github.com/pytest-dev/pluggy/pull/223/files#diff-60f61ab7a8d1910d86d9fda2261620314edcae5894d5aaa236b821c7256badd7
See: jazzband/pip-tools#806 (comment)
NicolasT added a commit that referenced this pull request Dec 17, 2020
Due to changes in `pluggy` (a dependency of `pytest`) using the
`importlib.metadata` module from the standard library instead of the
`importlib-metadata` package when running on Python >= 3.8, we need to
pin the `basepython` used in the `pip-compile` Tox env to the version
that's actually used in CI, otherwise `pip` complains during
installation of dependencies the `importlib-metadata` package is not
listed (with hashes) in some `requirements.txt`. As such, setting
`basepython` to `python3.6`, similar to 8a9104b.

Also, update the versions of `pip` and `pip-tools` used in the
`pip-compile` `tox` target, and use the `--allow-unsafe` flag which is
supposedly not really unsafe at all (and will become the default).

See: 8a9104b
Closes: #2897
Closes: #2898
See: pytest-dev/pluggy#222
See: https://github.com/pytest-dev/pluggy/pull/223/files#diff-60f61ab7a8d1910d86d9fda2261620314edcae5894d5aaa236b821c7256badd7
See: jazzband/pip-tools#806 (comment)
@bert-e bert-e closed this in 46f1f76 Dec 21, 2020
@bert-e bert-e closed this in #2986 Dec 21, 2020
@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github Dec 21, 2020

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

1 similar comment
@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github Dec 21, 2020

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

@dependabot dependabot bot deleted the dependabot/pip/tests/cryptography-3.2 branch December 21, 2020 23:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind:dependencies Pull requests that update a dependency file python Pull requests that update Python code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants