- Try empty passphrase first when opening a wallet, as all Trezors will have passphrase enabled by default by Trezor Suite by default.
This feature enables easier access to all users using disabled passphrase (or empty passhprase)
- If wallet address differs from device address with empty passphrase, another opening attempt is made, without passphrase suppression,
so user can enter his passhprase if using some. In this scenario, nothing changes to user, wallet opening just consumes one more call
to Trezor (get wallet address with empty passphrase)
- also change how m_passphrase is used. Previous version did not work well with recent passphrase entry mechanism change (made in Trezor),
thus this commit fixes the behaviour).
THROW_WALLET_EXCEPTION_IF(!dev_cold->get_public_address_with_no_passphrase(device_account_public_address),error::wallet_internal_error,"Cannot get a device address");
LOG_PRINT_L0("Wallet opened with an empty passphrase");
fetch_device_address=false;
dev_cold->set_use_empty_passphrase(true);
}else{
fetch_device_address=true;
LOG_PRINT_L0("Wallet opening with an empty passphrase failed. Retry again: "<<fetch_device_address);
dev_cold->reset_session();
}
}
if(fetch_device_address){
THROW_WALLET_EXCEPTION_IF(!hwdev.get_public_address(device_account_public_address),error::wallet_internal_error,"Cannot get a device address");
}
THROW_WALLET_EXCEPTION_IF(device_account_public_address!=m_account.get_keys().m_account_address,error::wallet_internal_error,"Device wallet does not match wallet address. If the device uses the passphrase feature, please check whether the passphrase was entered correctly (it may have been misspelled - different passphrases generate different wallets, passphrase is case-sensitive). "