Skip to content
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_Incoming): Use proper AES in the encrypted logs #6172

Closed
Tracked by #5606
LHerskind opened this issue May 3, 2024 · 0 comments · Fixed by #6269
Closed
Tracked by #5606

feat(Keys_Incoming): Use proper AES in the encrypted logs #6172

LHerskind opened this issue May 3, 2024 · 0 comments · Fixed by #6269
Assignees

Comments

@LHerskind
Copy link
Contributor

LHerskind commented May 3, 2024

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.

@github-project-automation github-project-automation bot moved this to Todo in A3 May 3, 2024
@LHerskind 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
@LHerskind LHerskind self-assigned this May 8, 2024
LHerskind added a commit that referenced this issue May 9, 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>
@github-project-automation github-project-automation bot moved this from Todo to Done in A3 May 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
1 participant