Explore >> Select a destination
|
You are here 
|
unixdigest.com | ||
| | | | |
www.niallkennedy.com
|
|
| | | | | In this post I will take a deeper look at the current best practices of the social Web from the point of view of its major data hubs. We will take a detailed look at the right and wrong ways to request user data from social hubs large and small, and outline some action items... | |
| | | | |
blog.gravatar.com
|
|
| | | | | Tired of traditional passwords? Discover how passkeys revolutionize authentication. Find practical usage examples and practical implementation guides. | |
| | | | |
janko.io
|
|
| | | | | Passkeys are a modern alternative to passwords, where the user's device performs the authentication, usually requiring some form of user verification (biometric identification, PIN). Passkeys are built on top of WebAuthn specification, which is based on public-key cryptography. Keypairs are created for each website, and the public key is sent to the server, while the private key is securely stored on the device. This makes passkeys: | |
| | | | |
carlschwan.eu
|
|
| | | A month ago, I started working on a new application to manage your passwords in Plasma. And while still at a PoC status, this weekend, it finally started to look like something almost usable, so it sounded like a good occassion to write a small blog post about it. The current name is "Keychain" or "Plasma Keychain" but this is subject to change and suggestions are more than welcome. My end goal is to provide a more future proof replacement to the ageing KWallet application. From a technical point of view, this is a fork of the internal of KeepassXC with a Kirigami GUI completely written from scratch. This means it uses the standardized Keepass format to store the passwords in the database which is implemented by many applications including on other platforms... | ||
