Search the Community
Showing results for tags 'two step verification'.
Found 3 results
Currently, it's only possible to get a two step verification code via text message or Google Authenticator. it’s important to keep my accounts as secure as possible, so I was really happy when Evernote announced that two-step verification is available to all Evernote users. I enable it immediately. But now i’m forced to use Google Authenticator. I’ve had to switch to Google Authenticator to copy my one-time-paswsword and quickly switch back to Evernote to paste it before it expires! It’s very stressful. For all my other accounts (that use two steps verification) I simply use 1Password (build in time-based one-time password (TOTP)). Only for Evernote I’ve had to install the Google Authenticator App. Hopefully Evernote will supports the time-based one-time password (TOTP) feature of the 1Password extension, so I don’t have to worry about it anymore.
I noticed that it doesn't seem possible to remove the primary phone number while two-step verification is enabled. Unfortunately, that weakens the security of two-step verification, even when using an authenticator app. This Wired article provides a great overview of the weakness of SMS-based two-step verification and its vulnerability to "sim swap" type attacks: https://www.wired.com/2016/06/hey-stop-using-texts-two-factor-authentication/ I'd love to see the ability to remove phone numbers as an override for authenticator-based two-step verification. I'd also love to see Evernote adopt the U2F protocol for improved two-factor security: https://www.yubico.com/solutions/fido-u2f/
First time I tried to set up two-factor authentication, on the final step the screen displayed like this - the overlay window was super tiny. I couldn't click or see anything. Reloaded the page to fix, but then the whole process was cancelled and I had to re-enable two-factor authentication. Second time it displayed ok. Screenshot attached. Note sure if this would be browser related or evernote problem. Firefox 51.0.1. Just sharing in case anyone runs into a similar issue.