You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
LHerskind
changed the title
feat(Keys_Incoming): Use proper AES in the encrypted logs header
feat(Keys_Incoming): Use proper AES in the encrypted logs
May 7, 2024
… computations (#6269)
Fixes#6172.
Also fixes an issue as the typescript AES was not doing proper padding.
Battling noir, good with help from @Thunkar.
---------
Co-authored-by: thunkar <gregojquiros@gmail.com>
Co-authored-by: David Banks <47112877+dbanks12@users.noreply.github.com>
Co-authored-by: Jan Beneš <janbenes1234@gmail.com>
The current implementation of a encrypted log header is using the AES oracle. It should be replaced with the actual AES.
Same is the case for the body.
Search for "6172" in the repo.
The text was updated successfully, but these errors were encountered: