-
Notifications
You must be signed in to change notification settings - Fork 122
chore(README): update README.md #1940
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
Merged
Merged
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
2a3c3c4
chore: update README.md
imabhichow 0091cde
chore: update README.md
imabhichow 04bf2e3
chore: update README.md
imabhichow c20682f
chore: update README.md
imabhichow 5aaee17
chore: update README.md
imabhichow b7f40a8
address feedback
imabhichow a31e015
address feedback
imabhichow 3828b65
Merge branch 'master' into imabhichow/readme
imabhichow e09e2ba
address feedback
imabhichow File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why the ? in
CryptoResult<byte[], ?>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The
?
is a wild card to keepencryptData
API compatible with previous releases.ESDK-Java's CryptoResult includes a definition of the actual Cryptographic Material Provider (MasterKey or MasterKeyProvider) as a Generic that can be refined at class initialization.
I am not sure if we ever refactored that
CryptoResult
class soIKeyring
orICryptographicMaterialProvider
could refine the Generic...There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We clearly did not:
https://github.com/aws/aws-encryption-sdk-java/blob/master/src/main/java/com/amazonaws/encryptionsdk/CryptoResult.java#L31
This means that following APIs are now broken for Keyring users:
CryptoResult.getMasterKeys
CryptoResult.getMasterKeyIds
Which... is not Great.
@imabhichow we should bring this up at Stand up.
Those APIs are NOT critical; one of them is even marked as deprecated.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking into the details here, this is not bad or even an issue.
K
is would be an explicit MasterKey.If no MaterKey or MasterKeyProviders are used,
then no one SHOULD expect a list of MasterKeyIDs to be populated.
We should probably write a test to assert that nothing wild happens,
like an Exception.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When using keyrings, the
CryptoResult.getMasterKeyIds
method returns an empty list during encryption.However, during decryption, CryptoResult.getMasterKeyIds throws a NULL POINTER EXCEPTION. This could be due to returning a DataKey with the master key set to null. I suppose we should expect similar behavior to encryption which is returning an empty llist of masterkeys. I'll try to look more into this.
I also think we should deprecate this method CryptoResult.getMasterKeyIds
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should have, yes.
And we should cut a PR to prevent the NPE.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With this pull request, CryptoResult.getMasterKeyIds is now deprecated and will return an empty list when we use keyrings.