Format-preserving encryption capabilities #17
Conversation
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
alberto-crossmint
changed the title
alberto-crossmint
changed the title
| @@ -67,7 +67,7 @@ export class CrossmintApiService extends XMIFService { | |||
| static createSignerInputSchema = z.object({ authId: z.string() }); | |||
| static createSignerOutputSchema = z.object({}); | |||
|
|
|||
| static sendOtpInputSchema = z.object({ otp: z.string() }); | |||
| static sendOtpInputSchema = z.object({ otp: z.string(), publicKey: z.string() }); | |||
There was a problem hiding this comment.
We add the public key for the TEE to derive the corresponding AES256 encryption key
| ciphertext: ArrayBuffer, | ||
| encapsulatedKey: ArrayBuffer, | ||
| { validateTeeSender }: { validateTeeSender: boolean } = { validateTeeSender: true } | ||
| async decrypt<T extends Record<string, unknown>, U extends string | ArrayBuffer>( |
There was a problem hiding this comment.
Integrated decrypt and decryptBase64 into a single function. Having both felt reduntant
| async getEncryptionData(): Promise<EncryptionData> { | ||
| // Key derivation | ||
|
|
||
| private async deriveAES256EncryptionKey(): Promise<CryptoKey> { |
There was a problem hiding this comment.
Here we derive the AES key for the FF1 algorithm!
| this.assertInitialized(); | ||
| // biome-ignore lint/style/noNonNullAssertion: asserted before | ||
| return this.suite.kem.serializePublicKey(this.ephemeralKeyPair!.publicKey); | ||
| private async serializePrivateKey(key: CryptoKey): Promise<ArrayBuffer> { |
There was a problem hiding this comment.
We were using the kem serialization function but this had a problem in which, when we deserialized and reconstructed the keys, the usages of the key were not re'included, so it will fail later when trying to use it. That's why we built this custom serialization/deserialization functions
devlyn37
approved these changes
May 7, 2025
| @@ -54,7 +54,7 @@ export class AttestationService extends XMIFService { | |||
| } | |||
|
|
|||
| private async fetchAttestationDoc(): Promise<AttestationDocument> { | |||
| const response = await fetch('https://tee-ts.onrender.com/attestation', {}); | |||
| const response = await fetch('http://localhost:3001/attestation', {}); | |||
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
FF1 is a NIST-approved format preserving encryption (FPE) algorithm. This allows us to compute an AES256-encrypted OTP-like payload from an OTP-like payload!
This PR creates a
FPEServicethat uses theencryptionServiceto derive an AES256-GCM key from the shared secret that is present after ECDH exchange that we already performed for HPKE and uses that symmetric key to perform the OTP encryption.This is disabled. To be enabled by just uncommenting the line in the send OTP handler.
Tested it by running a local instance of the iframe and performing encryption-decryption within it! Will test end to end and enable when the corresponding part lands on the TEE-ts side
Tested the whole flow with the code in https://github.com/Paella-Labs/tee-ts/pull/3