Explore >> Select a destination
|
You are here 
|
labanskoller.se | ||
| | | | |
supabase.com
|
|
| | | | | MFA Auth with enforcement via RLS | |
| | | | |
zserge.com
|
|
| | | | | Many of us use one-time passwords (OTP) regularly to log into different services. Most probably rely on Google Authenticator and similar tools. But what about building one by ourselves? | |
| | | | |
prezu.ca
|
|
| | | | | Part 3 is the last part in this short cycle. Here I'll explain all the details around Time-based One-Time Password algorithm. I'll finish up by also elaborating on things common to both, HMAC-Based One-Time Password algorithm: QR Codes used to easily transfer secrets from the server to the Authenticator app Base32 algorithm - used to store non-printable secret in a URI (effectively stored by the QR Codes mentioned above). TOTP One way to avoid the problems with lack of feedback between server and the app... | |
| | | | |
128bit.io
|
|
| | | GPG stands for GNU Privacy Guard, it's a public-key cryptography that can be used to digitally sign items like commits in Git. GPG provides a lot more functionality, but let's go into why you would want to digitally sign your Git commits. Git does not have any way to validate the author of a commit. When setting up a Git client on your system you are able to use any email address you desire. | ||
