• Fri. Dec 8th, 2023

GitHub introduces passwordless authentication

GitHub introduces passwordless authentication

GitHub Introducing password-free authentication to increase account security and provide a more seamless user experience.

With the goal of eliminating password-based breaches altogether, passkeys offer a secure and easy-to-use method of protecting user accounts. Unlike traditional security measures, Passkeys offer enhanced security by combining two-factor authentication (2FA) with enhanced user verification.

Passkeys require something known or known to the user (such as a fingerprint, face, or PIN) and possessed by the user (a physical security key or device). By leveraging these elements, GitHub can verify user identities without relying on passwords.

To enable passkeys on a GitHub account, users must navigate to the ‘Settings’ sidebar, access the ‘Feature Preview’ tab and select the option to enable passkeys. If enabled, users can upgrade qualified security keys to passkeys and register new passkeys.

Passkeys can be used across devices, and a new feature called cross-device authentication lets users sign in on a desktop by verifying the presence of their phone.

One of the main advantages of passkeys is the ability to completely replace passwords. When using passkeys on GitHub.com, user authentication works as two factors in one, eliminating the need for passwords.

Also, with extended browser support, passkeys can be automatically suggested by the browser’s autofill system on the login page, making the authentication process more efficient.

Passkeys offer sync across devices, ensuring users are never locked out of their accounts due to a lost key.

Depending on the passkey provider, syncing can happen automatically, leveraging services like iCloud, Google Password Manager, or password managers like 1Password or Dashlane.

For users with existing security keys, upgrading to passkeys is a simple process. Eligible security keys capable of verifying user identities, such as Touch ID, Windows Hello, or biometric hardware keys, can be upgraded to passkeys.

GitHub’s introduction of passkey authentication demonstrates the platform’s commitment to increasing account security while prioritizing user experience. By adopting passwordless authentication, GitHub aims to reduce the risk of data breaches caused by weak or compromised passwords.

With passkeys, developers can protect their accounts with ease and confidence, knowing that their sensitive information is protected from unauthorized access.

See also: The Reddit hacker’s demands include making API changes

Want to learn more about cybersecurity and the cloud from industry leaders? check out Cyber ​​Security and Cloud Expo Taking place in Amsterdam, California and London. The program is in collaboration with Digital Transformation Week.

Explore other upcoming enterprise technology events and webinars hosted by TechForge Here.

  • Ryan Doss

    Ryan is a senior editor at Techforge Media and has spent more than a decade covering cutting-edge technologies and interviewing leading industry leaders. He can often be seen at tech conferences with a strong coffee in one hand and a laptop in the other. If it’s geek, he’s probably into it. Find him on Twitter (@Gadget_Ry) or Mastodon (@gadgetry@techhub.social).

    View all posts

Tags: Cyber ​​Security, Cyber ​​Security, Github, Hacking, Infosec, Passkeys, Passwordless Authentication, Security

Leave a Reply

Your email address will not be published. Required fields are marked *