Dictionary attacks can automatically account for common letter substitutions and have made the argument in that comic outdated and extremely misleading.
I suppose I didn't write that comment particularly well since the criticism is more from computer science nerds than anything...let me start over.
You were telling me to not use random 30+ character passwords. Passwords that are like "Tr0ub4dor&3" are indeed extremely easy to crack and passwords like "correct horse battery staple" are not easily cracked. However, you are still better off with even a short randomly generated password like "tB[5_53#r=09" because it isn't based off of any logical pattern. I lengthen it to something more like "lnS(oS+bw8rXpEuLGG37sqz!4KnjZYOodwH'JXZFApT-jrIvCT" just because I can and call it a day.
My biggest thorn these days is having to open 1Password to get the app password, copy it, then paste it into the app every time. Hoping the APIs will provide cross-app integration while maintaining security.
A quicker way is to go up the the address bar of the page you are on and insert op for 1password before http and the URL will open in 1password browser. So ophttp://www.blah.com/login/blah
I did it to log in to Macrumors and post this comment.
Now if only they would figure out a way to make keychain work with Windows. I love Keychain and this sounds awesome, but I really can't start letting them make up passwords for me until it works with Windows too.
Hey does anyone know if this ever got implemented? I can't find any documentation on the Apple support website or references to this particular Continuity api on their site.
I tried the Gmail app and it didn't ask me to use Safari keychain information.