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
It seems the software uses encoding routines that do not run in constant-time on secrets. This is generally something that is avoided on application dealing with cryptography since it might lead to the leak of secrets due to cache timing attack.
One example in this codebase:
Util::generateRandomBytes(): returned value is passed into bin2hex and then used as IV, secrets…
…he-timing attacks (this does not affec to to cryptographic functions, which were already safe). Thanks to @LeSuisse for the feedback.
* [MOD] Temporary master password will never be saved in the event log.
Hello,
It seems the software uses encoding routines that do not run in constant-time on secrets. This is generally something that is avoided on application dealing with cryptography since it might lead to the leak of secrets due to cache timing attack.
One example in this codebase:
Util::generateRandomBytes()
: returned value is passed intobin2hex
and then used as IV, secrets…You can get more information on this in the following blog post from ParagonIE: https://paragonie.com/blog/2016/06/constant-time-encoding-boring-cryptography-rfc-4648-and-you
The text was updated successfully, but these errors were encountered: