awslabs/aws-encryption-sdk-specification issues and pull requests

#100 - docs: define how the default CMM uses a master key provider

Pull Request - State: closed - Opened by mattsb42-aws almost 5 years ago

#99 - chore: add basic gitignore

Pull Request - State: closed - Opened by mattsb42-aws almost 5 years ago

#98 - Define how the default CMM uses master key providers

Issue - State: closed - Opened by mattsb42-aws almost 5 years ago
Labels: Doc impact

#97 - [feature proposal] additional keyring trace entries

Issue - State: closed - Opened by mattsb42-aws almost 5 years ago
Labels: enhancement, Doc impact

#96 - review decrypt API output - add at least encryption context

Issue - State: open - Opened by mattsb42-aws almost 5 years ago - 1 comment

#95 - define how keyring trace manifests in the ESDK client interface and how users should interact with it

Issue - State: closed - Opened by mattsb42-aws almost 5 years ago - 5 comments

#94 - define client supplier interface and common manifestations

Issue - State: closed - Opened by mattsb42-aws almost 5 years ago - 2 comments

#93 - Add cache entry identifier formulas that the caching CMM needs to use

Issue - State: closed - Opened by mattsb42-aws almost 5 years ago - 1 comment

#92 - Fixed small typo

Pull Request - State: closed - Opened by WouterSchols almost 5 years ago

#91 - Raw RSA keyring public/private key inputs and validation

Issue - State: closed - Opened by mattsb42-aws almost 5 years ago - 9 comments
Labels: Doc impact

#90 - ExcludeRegions/LimitRegions Client Supplier Null/Empty Region Specification

Issue - State: closed - Opened by acioc almost 5 years ago - 9 comments

#89 - Adding Python and Java implementation links to keyring specs

Pull Request - State: closed - Opened by WesleyRosenblum almost 5 years ago - 1 comment

#88 - Fix flipped Caching CMM Postcondition

Pull Request - State: closed - Opened by lavaleri almost 5 years ago

#87 - Clarify halting vs non-halting failure behaviors

Issue - State: closed - Opened by mattsb42-aws almost 5 years ago

#86 - Remove unneeded cmm interface precondition

Pull Request - State: closed - Opened by lavaleri almost 5 years ago

#85 - Fix internal spec links

Pull Request - State: closed - Opened by lavaleri almost 5 years ago

#84 - Require users to describe intent on KMS Keyring constructor

Issue - State: closed - Opened by lavaleri almost 5 years ago - 2 comments

#83 - split the AWS KMS keyring specification

Issue - State: closed - Opened by mattsb42-aws almost 5 years ago - 2 comments
Labels: Doc impact

#82 - Specification Message Body: Inconsistency size encrypted content in regular frame

Issue - State: open - Opened by WouterSchols almost 5 years ago - 4 comments

#81 - Caching CMM MUST NOT call underlying CMM with plaintext length specified

Issue - State: open - Opened by lavaleri almost 5 years ago - 3 comments

#80 - The Caching CMM should never cache materials if the plaintext length is not know

Issue - State: open - Opened by seebees almost 5 years ago - 6 comments
Labels: Doc impact

#79 - Caching CCM should be clear about who provides the value for Cache TTL

Issue - State: closed - Opened by seebees almost 5 years ago - 1 comment

#78 - decrypt client API does not state that the keyring trace is needed on output

Issue - State: closed - Opened by mattsb42-aws almost 5 years ago

#77 - update PR template to ask about contributing issues

Issue - State: open - Opened by mattsb42-aws almost 5 years ago

#76 - add statement of intent and top-level requirements for multi-keyring encrypt HALT

Issue - State: closed - Opened by mattsb42-aws almost 5 years ago

#75 - add statements of intent for keyring encrypt and decrypt behavior

Issue - State: closed - Opened by mattsb42-aws almost 5 years ago

#74 - docs: Address KMS keyring on-encrypt issues

Pull Request - State: closed - Opened by mattsb42-aws almost 5 years ago

#73 - AWS KMS keyring encrypt behavior is incorrect

Issue - State: closed - Opened by mattsb42-aws almost 5 years ago
Labels: bug

#72 - Add maxBodySize behavior to Decrypt

Pull Request - State: closed - Opened by lavaleri almost 5 years ago - 1 comment

#71 - Specify optional algorithm suite on Encrypt input and clarify GetEncr…

Pull Request - State: closed - Opened by lavaleri almost 5 years ago - 1 comment

#70 - Clarify if keyring trace entries are a hard requirement on Materials structures

Issue - State: closed - Opened by robin-aws almost 5 years ago - 2 comments

#69 - Resolve issue #68

Pull Request - State: closed - Opened by juneb about 5 years ago - 1 comment

#68 - KeyIds definition is contradictory

Issue - State: closed - Opened by juneb about 5 years ago - 1 comment

#67 - clarify naming of AWS KMS keyring

Issue - State: closed - Opened by mattsb42-aws about 5 years ago - 3 comments
Labels: bug, Doc impact

#66 - Allow implementations that return results instead of mutating inputs

Issue - State: open - Opened by robin-aws about 5 years ago - 18 comments

#65 - Unspecified behavior for RawAESKeyring for invalid input EC

Issue - State: closed - Opened by lavaleri about 5 years ago

#64 - Support for asymmetric cryptographic operations

Issue - State: open - Opened by benkehoe about 5 years ago - 5 comments
Labels: enhancement

#63 - RawRSAKeyring OnDecrypt inconsistent with Keyring Interface

Issue - State: closed - Opened by lavaleri about 5 years ago - 2 comments

#62 - Defining the Master Key Provider Keyring

Pull Request - State: closed - Opened by WesleyRosenblum about 5 years ago - 1 comment

#61 - fix: Key IDs MUST have kms:Encrypt

Pull Request - State: closed - Opened by seebees about 5 years ago

#60 - OnEncrypt and OnDecrypt in KMS Keyring contains wrong key id for the keyring trace

Issue - State: closed - Opened by WesleyRosenblum about 5 years ago - 1 comment

#59 - AWS KMS Keyring SHOULD add custom identifier to KMS client user agent string

Issue - State: closed - Opened by mattsb42-aws about 5 years ago - 1 comment

#58 - Contradictory MUSTs in Caching CMM

Issue - State: closed - Opened by RustanLeino about 5 years ago - 3 comments

#57 - Mention that comparisons of plaintext data keys must be timing safe

Issue - State: open - Opened by robin-aws about 5 years ago - 4 comments

#56 - Rewrite Keyring interfaces in functional style

Pull Request - State: closed - Opened by robin-aws about 5 years ago - 5 comments

#55 - KMS Keyring should fail initialization if any keyId is malformed

Issue - State: closed - Opened by WesleyRosenblum over 5 years ago - 6 comments
Labels: enhancement

#54 - Correct key name and key namespace reference in OnDecrypt

Pull Request - State: closed - Opened by WesleyRosenblum over 5 years ago

#53 - Rewrite Keyring interface in functional style

Issue - State: open - Opened by robin-aws over 5 years ago

#52 - Resolve final frame content length inconsistency

Pull Request - State: closed - Opened by lavaleri over 5 years ago

#51 - Inconsistent MUST requirement in framed message format definition

Issue - State: closed - Opened by mattsb42-aws over 5 years ago - 1 comment
Labels: bug, Doc impact

#50 - Remove lines mandating region be specified by KMS keyring generator

Pull Request - State: closed - Opened by MatthewBennington over 5 years ago - 1 comment
Labels: doc change required

#49 - Define behavior for a KMS-Keyring when given an generator which is an alias

Issue - State: closed - Opened by MatthewBennington over 5 years ago - 2 comments

#48 - Clarify Message Body AAD Content Length field for framed data

Pull Request - State: closed - Opened by lavaleri over 5 years ago

#47 - Add KeyName/KeyNamespace terms to Keyring Interface spec

Issue - State: closed - Opened by lavaleri over 5 years ago

#46 - add master key and master key provider interface specs

Pull Request - State: closed - Opened by mattsb42-aws over 5 years ago

#45 - Key hierarchies and combinations

Issue - State: open - Opened by mattsb42-aws over 5 years ago - 4 comments
Labels: enhancement

#44 - Fix links

Pull Request - State: closed - Opened by lavaleri over 5 years ago

#43 - Updated README with an overview and list of current implementations

Pull Request - State: closed - Opened by ttjsu-aws over 5 years ago

#42 - Verification of version and type on deserialization base64 encoding error

Issue - State: closed - Opened by seebees over 5 years ago - 1 comment

#41 - Add license headers

Pull Request - State: closed - Opened by lavaleri over 5 years ago

#40 - KMSKeyring error handling

Issue - State: closed - Opened by seebees over 5 years ago - 4 comments

#39 - Add new keyring trace flag to indicate KMS Keyring property

Issue - State: closed - Opened by lavaleri over 5 years ago

#38 - Fix MessageBodyAAD ContentLength

Issue - State: closed - Opened by lavaleri over 5 years ago

#37 - Fix links

Issue - State: closed - Opened by lavaleri over 5 years ago

#36 - Import specification into github

Pull Request - State: closed - Opened by ttjsu-aws over 5 years ago

#35 - Adding Versioning Policy

Pull Request - State: closed - Opened by ttjsu-aws over 5 years ago

#34 - Add License Headers

Issue - State: closed - Opened by lavaleri over 5 years ago

#33 - Revise Cryptographic Materials Cache specification

Issue - State: closed - Opened by ttjsu-aws over 5 years ago - 1 comment

#32 - Keyring trace flag VERIFIED_ENCRYPTION_CONTEXT

Issue - State: closed - Opened by lavaleri over 5 years ago

#31 - Update to license to CC-BY-SA 4.0, Sample Code under MIT-0

Pull Request - State: closed - Opened by lavaleri over 5 years ago

#30 - Add the crypto format spec

Issue - State: open - Opened by ttjsu-aws over 5 years ago

#29 - Provider Info serialization in the AES Keyring/MKP

Issue - State: closed - Opened by ttjsu-aws over 5 years ago - 2 comments

#28 - Remove the term pseudo-ASN.1 structure

Issue - State: open - Opened by ttjsu-aws over 5 years ago

#27 - Add streaming decrypt spec

Issue - State: closed - Opened by ttjsu-aws over 5 years ago - 1 comment

#26 - Add streaming encrypt spec

Issue - State: closed - Opened by ttjsu-aws over 5 years ago - 1 comment

#25 - Remove message header as part of the decrypt API output

Issue - State: closed - Opened by ttjsu-aws over 5 years ago - 1 comment

#24 - Reduce redundancies in keyring specifications

Issue - State: closed - Opened by lavaleri over 5 years ago - 1 comment

#23 - Define encryption context reserved prefix

Issue - State: closed - Opened by lavaleri over 5 years ago

#22 - Fix message sample structures

Issue - State: open - Opened by lavaleri over 5 years ago

#21 - EDK Key Provider ID/Information field names

Issue - State: closed - Opened by lavaleri over 5 years ago - 1 comment

#20 - Write specification for KMS MK/MKP

Issue - State: open - Opened by lavaleri over 5 years ago - 1 comment

#19 - Write specification for Raw MK/MKP

Issue - State: open - Opened by lavaleri over 5 years ago - 1 comment

#18 - Write specification for MK Interface

Issue - State: closed - Opened by lavaleri over 5 years ago - 1 comment

#17 - Write specification for MKP Interface

Issue - State: closed - Opened by lavaleri over 5 years ago - 1 comment

#16 - Write specification for the KMS caching supplier

Issue - State: closed - Opened by lavaleri over 5 years ago - 1 comment

#15 - Write specification for KMS single client supplier

Issue - State: closed - Opened by lavaleri over 5 years ago - 2 comments

#14 - Update spec Definitions sections

Issue - State: closed - Opened by lavaleri over 5 years ago - 1 comment

#13 - Add ESDK Concepts to specification

Issue - State: closed - Opened by lavaleri over 5 years ago - 2 comments

#12 - define decryption contract for multi-keyring

Issue - State: open - Opened by lavaleri over 5 years ago - 1 comment

#11 - Define how the specification should deal with errors/failures

Issue - State: closed - Opened by lavaleri over 5 years ago - 1 comment

#10 - Add Test Vectors section to all documents

Issue - State: open - Opened by lavaleri over 5 years ago

#9 - Update algorithm-suites.md Security Considerations

Issue - State: open - Opened by lavaleri over 5 years ago

#8 - Update CONTRIBUTING.md

Issue - State: open - Opened by lavaleri over 5 years ago

#7 - Write README.md

Issue - State: closed - Opened by lavaleri over 5 years ago

#6 - Write message.md

Issue - State: open - Opened by lavaleri over 5 years ago

#5 - Add support for SHA384 and SHA512 for use with RSA OAEP wrapping algorithms

Issue - State: open - Opened by ttjsu-aws over 5 years ago - 1 comment

#4 - On decrypt path, the default CMM MUST remove the signature from the EC

Issue - State: open - Opened by ttjsu-aws over 5 years ago - 5 comments

GitHub / awslabs/aws-encryption-sdk-specification issues and pull requests