Google appears to be planning some added security for upcoming Chromebooks. The company’s Chromium code repository mentions a fingerprint sensor for Chrome OS, as first spotted by Chrome Unboxed.
Led by Apple, Samsung, and others, fingerprint sensors are currently the most popular—not to mention fastest—method of biometric authentication. Windows 10 PCs also use biometric authentication via Microsoft’s Windows Hello feature. Microsoft favors facial recognition and retina scanning in its Windows 10 devices, but it also supports fingerprint scanning.
It’s not clear how fingerprint scanning would work on Chromebooks. Presumably, it would be used instead of your Google password to sign in to your machine on a daily basis. Fingerprint scanning could also come in handy to authorize Google Play purchases once Android app support goes mainstream on Chrome OS.
Who knows? A little further down the road, Chrome OS could also support third-party web logins similar to what Microsoft is doing with Windows Hello in Microsoft Edge. In fact, that’s more than likely because Google, along with Microsoft, PayPal, and others, is working on a standard for biometric authentication for websites and web apps.
For now, however, Google and its Chromebook partners are just working on getting basic fingerprint scanning up and running. Chrome Unboxed says fingerprint scanning may debut with a rumored 360-degree convertible Chromebook codenamed ‘Kevin.’
Why this matters: Google is one of many companies trying to figure out a future where passwords are no longer used for authentication—or they’re at least deemphasized in favor of more convenient, yet secure, methods like biometric authentication. Google may also be trying to improve Chrome’s relationship to Android by adding key features the mobile OS already has. That’s especially important because users will expect Android apps on Chromebooks to work just as they would on a phone or tablet.
In addition to fingerprint scanning, Google is bringing PIN-based authentication to Chromebooks, as first noticed by OMG Chrome. The feature is already available in the Chrome OS Canary channel.