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 github.com/ProtonMail/go-crypto from 1.1.0-beta.0-proton to 1.1.2 #662

Merged

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Nov 11, 2024

Bumps github.com/ProtonMail/go-crypto from 1.1.0-beta.0-proton to 1.1.2.

Release notes

Sourced from github.com/ProtonMail/go-crypto's releases.

Release v1.1.2

What's Changed

Full Changelog: ProtonMail/go-crypto@v1.1.1...v1.1.2

Release v1.1.2-proton

What's Changed

This release is v1.1.2 with support for symmetric keys and automatic forwarding, both of which are not standardized yet.

Release v1.1.1

What's Changed

Full Changelog: ProtonMail/go-crypto@v1.1.0...v1.1.1

Release v1.1.1-proton

What's Changed

This release is v1.1.1 with support for symmetric keys and automatic forwarding, both of which are not standardized yet.

Release v1.1.0

What's Changed

This release adds full support for the new version of the OpenPGP standard, RFC 9580. In addition, the release introduces an improved non-backwards compatible v2 API. The API in the openpgp package remains fully backwards compatible while the new v2 API is located in a separate v2 package in openpgp.

For the full changes since v1.0.0, see the previous release notes. For the full changelog, see ProtonMail/go-crypto@v1.0.0...v1.1.0.

Changes since v1.1.0-beta.0:

  • Replace expiring curve448 integration test vector by @​lubux
  • Validate input key size in SEIPDv2 decryption by @​lubux

Changelog since v1.1.0-beta.0: ProtonMail/go-crypto@v1.1.0-beta.0...v1.1.0.

Release v1.1.0-proton

What's Changed

This release is v1.1.0 with support for symmetric keys and automatic forwarding, both of which are not standardized yet.

Commits
  • 2d2c789 feat(cleartext): Do not include line ending separator in plaintext (#242)
  • f8b3f21 Remove cleartext Encode header argument #239 (#240)
  • b97cc3c feat: Validate input key size in SEIPDv2 decryption (#236)
  • 20ab0e4 Replace expiring curve448 integration test vector (#235)
  • ef6d672 Fix SEIPDv2 packet parsing error messages (#215)
  • 4333135 Randomize v4 and v5 signatures via custom notation (#209)
  • 196c8f5 Allow parsing empty Key Flags subpackets (#214)
  • c25e074 Put support for reading v5 packets behind a feature flag (#212)
  • 3df78a3 Restrict S2K types (#213)
  • 3272cd7 ECDH with a v6 key must use the full fingerprint (#211)
  • Additional commits viewable in compare view

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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @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 dependabot bot added dependencies Pull requests that update a dependency file go Pull requests that update Go code labels Nov 11, 2024
Bumps [github.com/ProtonMail/go-crypto](https://github.com/ProtonMail/go-crypto) from 1.1.0-beta.0-proton to 1.1.2.
- [Release notes](https://github.com/ProtonMail/go-crypto/releases)
- [Commits](ProtonMail/go-crypto@v1.1.0-beta.0-proton...v1.1.2)

---
updated-dependencies:
- dependency-name: github.com/ProtonMail/go-crypto
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot force-pushed the dependabot/go_modules/github.com/ProtonMail/go-crypto-1.1.2 branch from bff4269 to 3688769 Compare November 11, 2024 22:15
@mergify mergify bot merged commit e4f36d5 into master Nov 11, 2024
5 checks passed
@dependabot dependabot bot deleted the dependabot/go_modules/github.com/ProtonMail/go-crypto-1.1.2 branch November 11, 2024 22:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file go Pull requests that update Go code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants