World Password Day 2024
Made with ♥ by FusionAuth
As developers, you are caught in a cosmic tug-of-war. On one side you want to protect your users' accounts. On the other side, you're dealing with users who set their passwords to "password" and wonder why their bank accounts are suddenly funding a llama sanctuary or buying Robux.
Passwords should be easy. And yet they aren't. Now it's more complicated than ever to balance security, ease of use, and like wtf is OAuth… amiright?
The first recorded instance of encryption was in Menet Khufu, an ancient city that bordered the Nile. Researchers have found inscriptions inside the tomb of Egyptian Noble Khnumhotep II, who lived around 3900 years ago. The scribe used a simple code of hieroglyphic substitution, changing one symbol for another to obscure the meaning of the inscriptions.
The message conceals a formula for pottery glaze which was used on clay tablets
The ancient Romans would utilize passwords through watchwords. The city guards would transcribe a nightly password on a wooden plank, and if someone didn’t know the watchword upon arrival at the gate they would not be permitted to enter.
On January 17th, 1920 the United States banned alcohol in a period called Prohibition. People created speakeasies, illegal drinking establishments that flew under the radar. To stay open in secret, speakeasies used code words to allow entry, similar to the Romans thousands of years prior. Some keywords included “swordfish, open sesame, and 42”
Fernando Corbato demonstrated the first password in an online system in 1961 for the MIT Compatible Time Sharing System (CTSS) (at MIT). Using a password felt like a straightforward solution to allow individual users to keep a private set of files.
The passwords would also limit the amount of time that they could spend on the system.
In 1966, graduate student Allan Scherr, fed up with the limits on his time available on his computer time, discovered he could print out the master password file on the system so that he could access other user accounts. And thus, the first password was hacked.
Curious if your passwords have been exposed?
Check out haveibeenpwned.com
Earlier versions of Unix used a password file, `/etc/passwd` to store all account information on a user, including hashed passwords. This data could be displayed by running cat /etc/passwd
.
In the 1970s salts were introduced. They make it more difficult for unauthorized users to determine the plain text value of passwords in the /etc/passwd
file by adding extra complexity to passwords before they are hashed and stored.
In the mid 1980s, password security was further enhanced by storing the password hashes separately in a file readable only by root called /etc/shadow. And now you relive the glory days of poor password security by getting a $cat /etc/passwd
shirt for free by downloading and installing FusionAuth!
Asymmetric cryptography, or public key infrastructure (PKI) emerged as a secure authentication technique. PKI was initially classified, and became public in the early 1990s, playing a big role in authentication.
In the 1980s, as passwords made the mainstream, so did the rise in hacking. The scope of the problem was so great that in 1985 the U.S. Department of Defense recommended the creation of the Department of Defense Password Management.
At that time, an eight character password containing letters and numbers could withstand six months of attack over a 300-baud modem.
One time passwords were developed by Leslie Lamport in 1984, an early example of passwordless authentication.
Sir Tim Berners-Lee founded the World Wide Web Consortium (W3C) at MIT/LCS to “shepherd the web, by developing open web standards.”
The Web Authentication API (WebAuthn) is developed and recommended by the W3C to strongly authenticate users through an authenticator, such as platform authenticators, roaming authenticators, or Near Field Communications (NFC). Logging in through a device is commonly referred to as using a passkey.
Passwords are more vulnerable than ever. In 2023, any six character password string containing any mix of letters, numbers, and symbols was susceptible to being brute force hacked instantly.
As the problem grows, platforms are requiring more complex passwords, adding layers on top passwords, or dropping passwords altogether for other methods, including multi-factor authentication, social sign on, passkeys, and more. World Password Day was created in 2013 by Intel to raise awareness about password security, and why it’s so harmful to businesses and developers.
As developers, you have more considerations than ever – you don’t want your users to feel like they are playing the password game when creating an account, after all, do you?
So, dear developers, let’s raise our coffee mugs (or beer glasses) to World Password Day. May your code be bug-free, your APIs RESTful, and hope that your users enjoy a password free future.
If all goes well, hopefully you won’t have to answer any more questions from your parents on how to reset their passwords or use a “password manager”.
Of company data breaches are caused by weak passwords.
Stolen passwords on the dark web since 2017.
Attacks blocked by multi-factor authentication.
Users affected by a Twitter Bug.
If you are looking to modernize your login experience, check out these resources we’ve put together:
Don't get left in the dust with passwords. Protect your users, improve their experience, and drive value using passkeys.
WebAuthn is the new way for people to authenticate themselves with web applications. Jump in to the standard!
A Brief History of Cryptography • Cypher
Privileged Passwords • Beyondtrust
A Concise History of Public Key Infrastructure • cdn.ymaws
The First Password To Be Hacked • FusionAuth
Password Statistics You Should Know • financesonline
1985 called. They want their passwords back! • tulane.edu
A Brief History of Passwords • dashlane.com
A Reminder We're Still Using Crackable Tech • cnet.com