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

x/crypto/openpgp: ReadMessage does not support encrypted private key #17845

Closed
jeanlucmongrain opened this issue Nov 8, 2016 · 2 comments
Closed

Comments

@jeanlucmongrain
Copy link

If a keyring used with ReadMessage hold keys that are decrypted aren't used to decrypt the packet.EncryptedKey.

Prompt function should be used to decrypt the private key.

@jeanlucmongrain
Copy link
Author

Fixed in https://golang.org/cl/32890

@bradfitz bradfitz changed the title x/crypto/openpgp ReadMessage do not support encrypted private key x/crypto/openpgp: ReadMessage does not support encrypted private key Nov 8, 2016
@bradfitz bradfitz added this to the Unreleased milestone Nov 8, 2016
@FiloSottile
Copy link
Contributor

Per the accepted #44226 proposal and due to lack of maintenance, the golang.org/x/crypto/openpgp package is now frozen and deprecated. No new changes will be accepted except for security fixes. The package will not be removed.

If this is a security issue, please email security@golang.org and we will assess it and provide a fix.

If you're looking for alternatives, consider the crypto/ed25519 package for simple signatures, golang.org/x/mod/sumdb/note for inline signatures, or filippo.io/age for encryption. You can read a summary of OpenPGP issues and alternatives here.

If you are required to interoperate with OpenPGP systems and need a maintained package, we suggest considering one of multiple community forks of golang.org/x/crypto/openpgp. We don't endorse any specific one.

@golang golang locked and limited conversation to collaborators Mar 29, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants