Sourced from github.com/ProtonMail/go-crypto's releases.
Release v1.1.2
What's Changed
- Cleartext Framework: Exclude the line-ending separator when decoding plaintext by
@lubux
in ProtonMail/go-crypto#242Full Changelog: https://github.com/ProtonMail/go-crypto/compare/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
- Fix
clearsign.Encode
backwards compatibility #239 by@mdosch
in ProtonMail/go-crypto#240Full Changelog: https://github.com/ProtonMail/go-crypto/compare/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 separatev2
package inopenpgp
.For the full changes since
v1.0.0
, see the previous release notes. For the full changelog, see https://github.com/ProtonMail/go-crypto/compare/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
: https://github.com/ProtonMail/go-crypto/compare/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.
v1.1.0-beta.0-proton
This pre-release is v1.1.0-beta.0 with support for symmetric keys and automatic forwarding, both of which are not standardized yet.
v1.1.0-beta.0
What's Changed
- Allow Salted S2K for high-entropy passphrases by
@twiss
in ProtonMail/go-crypto#219- fix data race in getEd25519Sk by
@DmitriyMV
in ProtonMail/go-crypto#220- Add back crypto.Signer support for ECDSA signing keys. by
@doryiii
in ProtonMail/go-crypto#227
... (truncated)
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)f6ad483
No v6 ECC keys with legacy OIDs (#234)77090fe
Fix ECDH using v6 keys (#233)7852179
Add support for keyserver preferences and preferred keyserver (closes #206)
(...2add693
Add back crypto.Signer support for ECDSA signing keys (#227)0f7b935
ci: Fix CI for v1 interoptest (#229)b5837fa
ci: Change gosop branch for gopenpgp-v2 to gosop-gopenpgp-v2 (#224)