, 13 tweets, 3 min read
If you follow @troyhunt and @lukew you know how bad things are around passwords, password forms, and password requirements. At the same time you're thinking: "it can't be *that* bad, can it?"

Oh, boy. A thread with nine examples

1/12
My laptop was stolen. So I decided to go through ~300 accounts stored in my 1password looking for weak passwords, 10-year old passwords etc. And updating them.

I updated ~50 accounts. Too bad I was busy changing passwords and not taking screenshots. Here's what I found:

2/12
- If you use a password manager, you will have to copy paste the new generated password into the "New password/Reset password form".

Pasting text will not trigger form validation. You have to at least delete and re-type a character. The most common problem.

3/12
- "Your password must be less than 20 characters" (PayPal)

4/12
- Any number of third-party scripts will be running on any page of your account, including password reset pages.

A reCaptcha on a password reset page? Why not? (PragProg)

5/12
- You registered with an email, but you have to log in with a username, or vice versa (Wordpress)

6/12
- Effing SPAs. Click "Sign In" button, provide user name and password, get shown front page again with "Sign in". 10-20 seconds later it's replaced with relevant account links

7/12
- Password reset not available in the app, or on the website, or in the mobile version of the website, and you can't get out of the mobile version. (Slack is guilty of at least one of them)

8/12
- Where would you put the link to change your password? How about create a button at the very button of your "edit profile" page right next to "Update Data" button (Sunfleet)

9/12
- Password reset links go through trackers (sometimes third party trackers because you know, you gotta track clicks in emails)

10/12
- Central login hubs and account management systems that lose your login status, end up in endless redirects, know who you are in only half of connected systems. Or keep you logged in when you've logged out. (Jetbrains, Google, Yahoo, Microsoft, the list goes on)

11/12
Everyone is guilty: big companies, small companies, dev and user darlings.

The next security or data breach, or stolen accounts? I can't imagine why it would ever happen in a security-conscious industry like ours.

If you've reached this, go and check your passwords :)

12/12
@threadreaderapp Please, unroll
Missing some Tweet in this thread?
You can try to force a refresh.

Like this thread? Get email updates or save it to PDF!

Subscribe to Dmitrii
Profile picture

Get real-time email alerts when new unrolls are available from this author!

This content may be removed anytime!

Twitter may remove this content at anytime, convert it as a PDF, save and print for later use!

Try unrolling a thread yourself!

how to unroll video

1) Follow Thread Reader App on Twitter so you can easily mention us!

2) Go to a Twitter thread (series of Tweets by the same owner) and mention us with a keyword "unroll" @threadreaderapp unroll

You can practice here first or read more on our help page!

Follow Us on Twitter!

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just three indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3.00/month or $30.00/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!