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

Create FAQ for common errors on encrypt/decrypt #305

Open
seebees opened this issue Apr 21, 2020 · 3 comments
Open

Create FAQ for common errors on encrypt/decrypt #305

seebees opened this issue Apr 21, 2020 · 3 comments

Comments

@seebees
Copy link
Contributor

seebees commented Apr 21, 2020

Errors can bubble up from the encrypt/decrypt functions.
It would be nice to have clear explanations for common errors.

In creating this documentation,
the error messages can also be re-evaluated for clarity.

See #152 as an example.

@holmser
Copy link

holmser commented May 7, 2020

"unencryptedDataKey has not been set" and "Noop keyring is not allowed: Set a keyId or discovery" are the two that have been giving me trouble so far.

@monscamus
Copy link

monscamus commented Nov 6, 2020

Definitely backing @holmser on those clearer error messages - also in related business when the IAM permissions aren't quite right it would be nice to get a message that says insufficient IAM privileges rather than the cryptic null parameter not allowed which I think you tend to get at the moment.

@metalcamp
Copy link

I get following error: "unencryptedDataKey has not been set" during decryption as well.

Following example here: https://github.com/aws/aws-encryption-sdk-javascript/blob/master/modules/example-node/src/aes_simple.ts using Raw AES keyring in example here.

Only difference being I split up encryption and decryption steps into separate functions.

What am I missing? Is KMS required even if explicitly want to avoid it, for example using Hashicorp Vault for storing secrets?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants