How many passwords do you have? 5? 15? 30? Have you started to use a password program to store all these hated passwords or do you just use the same password for everything? Well, have no fear… Google is planning on changing your life. The idea is very futuristic and cool. Some people are adamantly opposed to this though. I think as long as we have insurance on the level of security it will get people on board.
In the meantime here are some other alternatives to pesky password management that we use at Moka.
Clef: Sign into any of your websites with your phone. It’s so much more secure than the old password and user name login. However, you better keep your phone charged so you can access your websites when you need to.
Passpack: Store your passwords in a secure place. You do need a password to get into passpack though. And don’t forget it or you will have to create a new account and start over. There is no recovery.
Read the article below – what do you think?
Google is Planning to Get Rid of Passwords
/
Google is planning to get rid of passwords, and switch entirely towards a new system of authentication. Currently codenamed as Project Abacus, this new method of authentication is one of Google’s top innovative entities for the current year.
Basically, the idea involves using a set of biometric readings based on smartphone usage in lieu of passwords or SMS verification. As such, Project Abacus will lock or unlock your devices on the basis of trust score — it will monitor the manner in which you interact with your smartphone, voice and speech patterns, the way in which you type, your face or other biometrics, location and travel habits, and so on. Thereafter, it will evolve a method based on such data to identify “you”, and authenticate you accordingly.
Of course, this sounds pretty fancy and futuristic — the fact that your smartphone will truly be smart enough to “identify” you, and act accordingly. It is still in development, but more and more users are speaking in favor of it.
However, those against the concept of Abacus are strong too. Breach of privacy, access to user behavior and possibilities of a security issue, etc. are just some of the arguments against Project Abacus. More importantly, its practical implementation too is questionable — assuming Abacus identifies a user on the basis of their current behavior, what if the said user’s behavior changes due to a life-altering accident (say, a physical disability)? How will Abacus adapt to such changes and more importantly, how will it verify identity immediately after such changes?
