This is the tracking issue for kage MVP. Below are the requirements to achieve our first goal of making kage compatible with age.

API requirements

The requirements are divided into 3 sections - AgeFile, AgeKey, and Age Client. Once all the requirements are complete we will be able to generate age keys and use those keys to encrypt and decrypt data.

AgeFile

• Implement methods to parse AgeHeader
• Implement methods to write AgeHeader
• Implement methods to parse AgeBody
• Implement methods to write AgeBody
• Implement methods to parse AgeFile
• Implement methods to write AgeFile

AgeKey

• Implement methods to parse AgePublicKey
• Implement methods to write AgePublicKey
• Implement methods to parse AgePrivateKey
• Implement methods to write AgePrivateKey
• Implement methods to parse AgeKey
• Implement methods to write AgeKey

Age Client

• Implement methods to parse and generate X25519 recipients
• Implement crypto methods for X25519 recipients
• Implement methods to parse and generate X25519 identity
• Implement crypto methods for X25519 identity
• Implement a method that takes plaintext and a list of recipients and returns an AgeFile object
• Implement a method that takes an AgeFile and an identity and returns the decrypted data
• Implement convenience methods for library users
• Document public API

Final validation

• Pass all tests from the C2SP/CCTV age test suite