RE: LeoAuth Login Method Update | Security and LocalStorage vs. Cookies
You are viewing a single comment's thread:
That was a fast response. Good for the team.
So when people want to do transactions that require the Active Key, like transfers and power ups, they will be prompted to download keychain / install the extension, in orden to proceed, right?
0
0
0.000
Great question @tsunsica! For LeoAuth, it will prompt you to paste your active key and sign for that singular transaction. No remnants of that key will stay in LocalStorage or be broadcast in any way
For Keystore, it will ask you to select your Keystore file and Decryption Password in order to sign for the transaction. Similar to LeoAuth, no keys are getting broadcast and no remnants will remain in your browser
The dialogue that reminds users that they are using a convenient but slightly less secure method to sign transactions than Keychain will be present
Awesome! That is great for LeoAuth, an improvement since the previous version didn't have that option and you had to log out again, adding the active key. More secure but also more convenient!