Releases: ProtonMail/gopenpgp
Pre-Release v3.0.0-beta.2-proton
This release is v3.0.0-beta.0 with support for symmetric keys and automatic forwarding, both of which are not standardized yet.
Changes compared to v3.0.0-beta.1-proton
- Updates key encryption in the proton profile to match GopenPGP v2
Pre-Release v3.0.0-beta.1-proton
This release is v3.0.0-beta.0 with support for symmetric keys and automatic forwarding, both of which are not standardized yet.
Pre-release v2.8.0-beta.1-proton
This release is v2.8.0-beta.0 with support for symmetric keys and automatic forwarding, both of which are not standardized yet.
Pre-Release v3.0.0-beta.0
Pre-Release v2.8.0-beta.0
Added
func (key *Key) GetSHA256Fingerprint() (fingerprint string)
Changed
- Update go-crypto to 1.1.0-beta.0.
Full Changelog: v2.8.0-alpha.1...v2.8.0-beta.0
Pre-Release v3.0.0-alpha.4-proton
This release is v3.0.0-alpha.4 with support for symmetric keys and automatic forwarding, both of which are not standardized yet.
Pre-Release v3.0.0-alpha.4
Changed
- Update go-crypto to
1.1.0-alpha.4
. - Remove logic to get a profile by name.
- Reduce preset profiles to
Default
,RFC4880
, andRFC9580
. - Update go-crypto to check signature details of binding signatures.
Pre-Release v3.0.0-alpha.3-proton
This release is v3.0.0-alpha.3 with support for symmetric keys and automatic forwarding, both of which are not standardized yet.
Pre-Release v3.0.0-alpha.3
Added
- API to armor data with the option to remove the checksum
Changed
- All armor functions append a checksum per default for compatibility with certain libraries although the Crypto Refresh advises not to.
- The
Encryption
andSign
handle now append a checksum when armoring. If the produced OpenPGP packets are Crypto Refresh packets, the checksum is not appended as mandated by the crypto-refresh.
Pre-Release v3.0.0-alpha.2-proton
This release is v3.0.0-alpha.2 with support for symmetric keys and automatic forwarding, both of which are not standardized yet.