-
Notifications
You must be signed in to change notification settings - Fork 236
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
feat(Keys_Viewing): Make AES available in noir #5866
Comments
Closed
FWIW there was a community implementation in pure Noir: https://github.com/TaceoLabs/noir-aes If we already have a good implementation in barretenberg we certainly should blackbox it 👍 |
This was referenced Apr 22, 2024
Merged
Thunkar
added a commit
that referenced
this issue
May 7, 2024
Closes #5866 Adds AES128 as a blackbox function, exposing the existing functionality from barretenberg. Data is padded using PKCS#7 --------- Co-authored-by: Tom French <[email protected]>
AztecBot
pushed a commit
to AztecProtocol/barretenberg
that referenced
this issue
May 8, 2024
Closes AztecProtocol/aztec-packages#5866 Adds AES128 as a blackbox function, exposing the existing functionality from barretenberg. Data is padded using PKCS#7 --------- Co-authored-by: Tom French <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For the note encryption we need to have some encryption decryption available. As it looks atm, we will be using AES, so we need to have some AES implementation available.
BB already have an implementation so ideally we can simply expose that as a blackbox function, otherwise we need an implementation in pure noir.
We would very much want not do have the pure noir as it would be a pain to broadcast vs few calls to blackbox functions.
The text was updated successfully, but these errors were encountered: