Bump cryptography from 35.0.0 to 36.0.0

[dependabot]

Bumps cryptography from 35.0.0 to 36.0.0.

Changelog

Sourced from cryptography's changelog.

36.0.0 - 2021-11-21

* **FINAL DEPRECATION** Support for ``verifier`` and ``signer`` on our
  asymmetric key classes was deprecated in version 2.1. These functions had an
  extended deprecation due to usage, however the next version of
  ``cryptography`` will drop support. Users should migrate to ``sign`` and
  ``verify``.
* The entire :doc:`/x509/index` layer is now written in Rust. This allows
  alternate asymmetric key implementations that can support cloud key
  management services or hardware security modules provided they implement
  the necessary interface (for example:
  :class:`~cryptography.hazmat.primitives.asymmetric.ec.EllipticCurvePrivateKey`).
* :ref:`Deprecated the backend argument<faq-missing-backend>` for all
  functions.
* Added support for
  :class:`~cryptography.hazmat.primitives.ciphers.aead.AESOCB3`.
* Added support for iterating over arbitrary request
  :attr:`~cryptography.x509.CertificateSigningRequest.attributes`.
* Deprecated the ``get_attribute_for_oid`` method on
  :class:`~cryptography.x509.CertificateSigningRequest` in favor of
  :meth:`~cryptography.x509.Attributes.get_attribute_for_oid` on the new
  :class:`~cryptography.x509.Attributes` object.
* Fixed handling of PEM files to allow loading when certificate and key are
  in the same file.
* Fixed parsing of :class:`~cryptography.x509.CertificatePolicies` extensions
  containing legacy ``BMPString`` values in their ``explicitText``.
* Allow parsing of negative serial numbers in certificates. Negative serial
  numbers are prohibited by :rfc:`5280` so a deprecation warning will be
  raised whenever they are encountered. A future version of ``cryptography``
  will drop support for parsing them.
* Added support for parsing PKCS12 files with friendly names for all
  certificates with
  :func:`~cryptography.hazmat.primitives.serialization.pkcs12.load_pkcs12`,
  which will return an object of type
  :class:`~cryptography.hazmat.primitives.serialization.pkcs12.PKCS12KeyAndCertificates`.
* :meth:`~cryptography.x509.Name.rfc4514_string` and related methods now have
  an optional ``attr_name_overrides`` parameter to supply custom OID to name
  mappings, which can be used to match vendor-specific extensions.
* **BACKWARDS INCOMPATIBLE:** Reverted the nonstandard formatting of
  email address fields as ``E`` in
  :meth:`~cryptography.x509.Name.rfc4514_string` methods from version 35.0.
The previous behavior can be restored with:
name.rfc4514_string({NameOID.EMAIL_ADDRESS: &quot;E&quot;})

Allow
:class:~cryptography.hazmat.primitives.asymmetric.x25519.X25519PublicKey
and
:class:~cryptography.hazmat.primitives.asymmetric.x448.X448PublicKey to
be used as public keys when parsing certificates or creating them with
</tr></table>

... (truncated)

Commits

• 5d21990 Bump for 36.0.0 release (#6643)
• d09e1ed Final polish on removing backends from places they aren't required (#6644)
• 5bd0c10 allow parsing of nonstandard country name and jurisdiction country name (#6641)
• 2b22df1 remind people we're going to remove verifier/signer (#6640)
• b14285e Simplify the code in the AEAD test (#6638)
• 8be0f79 Added a CI job for 3.11-dev (#6637)
• a9f101f Reduce number of windows builders (#6636)
• 60c846f Make randomorder a regular job and not a distro one (#6633)
• ccbcd46 Remove unused attributes (#6631)
• cbc7861 Try removing line whose purpose I don't understand (#6632)
• Additional commits viewable in compare view

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)

[Dreamsorcerer]

Still merging broken PRs. Any reason not to move to personal access token, as suggested by the documentation?

[webknjaz]

A personal access token would need us to maintain a separate "robot" account having too much access to the org. But it's possible to use a GitHub App token, I guess.
I wonder if this is somehow caused by the fact that Dependabot is somehow special-cased by GitHub. I have a feeling that it's their bug.

[Dreamsorcerer]

It's just because it doesn't trigger a workflow run, right? So, the issue is the token, rather than dependabot.

https://docs.github.com/en/actions/learn-github-actions/events-that-trigger-workflows#triggering-new-workflows-using-a-personal-access-token

[webknjaz]

@Dreamsorcerer it did trigger the workflow run but that somehow wasn't taken into account. Let me enable the new shiny feature of requiring the checks to be produced by a certain integration (previously they can be produced by any GitHub App, not just GHA). This probably won't fix it, though. I haven't had time to experiment and learn why this is happening actually.

[webknjaz]

@Dreamsorcerer you wouldn't believe in what repo I've found the cause of this bug!

🤯🤯🤯🤯🤯🤯🤯🤯🤯🤯🤯🤯🤯 pyca/cryptography#6512

[webknjaz]

@Dreamsorcerer this is how we'll put an end to broken auto-merges: #6369.