fix(deps): update module github.com/protonmail/gopenpgp/v2 to v3#2772
Open
renovate[bot] wants to merge 1 commit into
Open
fix(deps): update module github.com/protonmail/gopenpgp/v2 to v3#2772renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
Contributor
Author
ℹ️ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This PR contains the following updates:
v2.9.0→v3.4.1Release Notes
ProtonMail/gopenpgp (github.com/ProtonMail/gopenpgp/v2)
v3.4.1Compare Source
What's Changed
Full Changelog: ProtonMail/gopenpgp@v3.4.0...v3.4.1
v3.4.0Compare Source
What's Changed
Added
InsecureAllowAllKeyFlagsWhenMissingprofile option. Allows usage of keys without key flags.Changed
Full Changelog: ProtonMail/gopenpgp@v3.3.0...v3.4.0
v3.3.0Compare Source
What's Changed
Added
Changed
Full Changelog: ProtonMail/gopenpgp@v3.2.1...v3.3.0
v3.2.1Compare Source
What's Changed
Fixed
Full Changelog: ProtonMail/gopenpgp@v3.2.0...v3.2.1
v3.2.0Compare Source
What's Changed
Added
Changed
1.22.0.v1.2.0.pkgs/errorsdependency.Full Changelog: ProtonMail/gopenpgp@v3.1.3...v3.2.0
v3.1.3Compare Source
What's Changed
Changed
v1.1.6Full Changelog: ProtonMail/gopenpgp@v3.1.2...v3.1.3
v3.1.2Compare Source
What's Changed
Changed
v1.1.5Full Changelog: ProtonMail/gopenpgp@v3.1.1...v3.1.2
v3.1.1Compare Source
What's Changed
Changed
v1.1.4Full Changelog: ProtonMail/gopenpgp@v3.1.0...v3.1.1
v3.1.0Compare Source
What's Changed
Added
Changed
profile.Custom.AllowWeakRSAtoprofile.Custom.InsecureAllowWeakRSAv1.1.3Full Changelog: ProtonMail/gopenpgp@v3.0.0...v3.1.0
v3.0.0Compare Source
What's Changed
New simplified and unified API
GopenPGP v3 introduces a new unified API for high level OpenPGP operations. In comparison to GopenPGP v2, where similar functions were dispersed across different types and required varying implementations for the same operations, GopenPGP v3 consolidates these functions into a consistent interface. Now, operations such as Sign, Verify, Encrypt, Decrypt, and Key generation are each accessible through a unified, builder like API, simplifying integration and enhancing code readability across cryptographic workflows.
However, applications migrating from v2 to v3 will need to update their API calls, as the changes are not backward-compatible. This means that all previous API calls must be rewritten to align with the new, unified API structure. GopenPGP v3 supports the migration process by offering extensive documentation and practical examples. We recommend upgrading to v3 for the latest features and improvements, but we'll continue to support GopenPGP v2 for the time being. Our support includes ongoing bug fixes and minor feature updates to ensure stability and functionality for existing users.
For usage examples of the new API, see the README. For the full documentation, see https://pkg.go.dev/github.com/ProtonMail/gopenpgp/v3.
Profiles
GopenPGP v3 introduces the concept of profiles, enabling applications to configure OpenPGP algorithm selection based on their specific needs. For most applications, the provided preset profiles offer robust and secure defaults, eliminating the need for additional configuration.
RFC 9580 and Interoperability
GopenPGP v3 adds full support for the latest OpenPGP specification, RFC 9580. Compliance with the specification has also been significantly enhanced, as confirmed by the results in the OpenPGP interoperability test suite. These enhancements in GopenPGP v3 are possible by leveraging a new API in the go-crypto fork, which enables a range of improvements in functionality, compliance, and performance.
Go Mobile Support
GopenPGP v3 aims to be fully compatible with Gomobile to provide an API for mobile platforms. For this reason, the library defaults to a builder-like pattern, which is less commonly used in Go. All code that is only relevant for mobile platforms has been moved to the
mobilemodule.Extending Functionality
GopenPGP v3 introduces a streaming interface across all APIs, enabling memory efficient processing of large data.
Additionally, it extends the library's functionality with various improvements, such as:
Full Changelog: ProtonMail/gopenpgp@v2.7.5...v3.0.0.
Changelog since v3.0.0-beta.0: ProtonMail/gopenpgp@v3.0.0-beta.0...v3.0.0.
v2.10.0Compare Source
What's Changed
Changed
v1.4.1.1.23.0.Full Changelog: ProtonMail/gopenpgp@v2.9.0...v2.10.0
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.