v2.6.0
Security Update
Fixes bug that could leave unencrypted keys in memory after entering the spending password when signing transactions in multisignature wallets.
-
Who is affected:
Users that have the
spending password
set, in multisignature wallets m-of-n in which m>1. -
How are affected:
After entering the password and signing a transaction in multisignature wallets, and only after adding the 2nd or later signatures, the wallet keys can stay unencrypted. If a new TX need to be signed, the password will not be asked. The unencrypted keys will stay on memory as long as the app is open.