|
You are here |
obem.be | ||
| | | | |
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: | |
| | | | |
jonwillia.ms
|
|
| | | | | Notes on personal projects | |
| | | | |
textslashplain.com
|
|
| | | | | Passwords have lousy security properties, and if you try to use them securely (long, complicated, and different for every site), they often have horrible usability as well. Over the decades, the industry has slowly tried to shore up passwords' security with multi-factor authentication (e.g. one-time codes via SMS, ToTP authenticators, etc) and usability improvements (e.g.... | |
| | | | |
developerlife.com
|
|
| | | TLS is the backbone of web security. We will explore using TLS with Rust, and CFSSL to create a certificate authority to issue self signed certificates & keys. We will also create a server and client that communicate securely over the network using tokio and upgrade insecure TcpStream to TLSStream, and work with TLSAcceptor and TLSConnector. | ||