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
We have a privacy leak in encryption functionality (look for TODO(#12749) in the codebase to find where) because the each field of the AES log contains only 31 bytes of info while other kind of logs will contain full fields of info. We currently use only the AE128 encryption so this is not a problem currently on master but it will be a problem once the other schemes are used.
Having the code overfitted for AES128 is not acceptable
The text was updated successfully, but these errors were encountered:
benesjan
changed the title
Make AES log indistinguisable from Poseidon one
Make AES log indistinguisable from the Poseidon one
Mar 14, 2025
We have a privacy leak in encryption functionality (look for TODO(#12749) in the codebase to find where) because the each field of the AES log contains only 31 bytes of info while other kind of logs will contain full fields of info. We currently use only the AE128 encryption so this is not a problem currently on master but it will be a problem once the other schemes are used.
Having the code overfitted for AES128 is not acceptable
The text was updated successfully, but these errors were encountered: