☰
×
Login Register an account
Top Submissions Explore Upgoat Search Random Subverse Random Post Colorize! Site Rules Donate
34

Creating a password

submitted by kammmmak to whatever 5 monthsDec 6, 2024 08:43:07 ago (+34/-0)     (files.catbox.moe)

https://files.catbox.moe/0pbgvl.jpg



15 comments block

sort by: hot new top old low

[ - ] RMGoetbbels 4 points 5 monthsDec 6, 2024 09:58:10 ago (+4/-0)

been there

[ - ] Imsickofmakingusernames 2 points 5 monthsDec 6, 2024 18:06:45 ago (+2/-0)

Kind of like being sick of making user names

[ - ] 3Whuurs 1 point 5 monthsDec 7, 2024 03:36:08 ago (+1/-0)

I have exactly these types of passwords from exactly this kind of experience.

Side note.
Are these “1Password” type services worth while?

[ - ] RabbiKinderschtupper 2 points 5 monthsDec 6, 2024 11:06:59 ago (+2/-0)

I work in IT. This is accurate.

[ - ] 2Drunk 3 points 5 monthsDec 6, 2024 14:51:29 ago (+3/-0)

Why the fuck do I have to change it every 30 days. You think I can remember that shit? I'm just going to write it down and keep it in my desk now! How safe is that?

[ - ] Trope 1 point 5 monthsDec 6, 2024 23:19:20 ago (+1/-0)

Just write it down on a post-it note and keep it on your monitor.

[ - ] Prairie 2 points 5 monthsDec 6, 2024 10:14:53 ago (+2/-0)

And if you use a string of truly random characters, it either bitches that it's not secure enough, or gives a random error because it has some punctuation it doesn't like (even though it demands it).

[ - ] x0x7 2 points 5 monthsDec 6, 2024 10:06:50 ago (+2/-0)

If it's able to tell that quickly that a password is already in use then they aren't storing passwords correctly.

Maybe sites should worry more about their end of password management and let users do what they want.

[ - ] Rawrination 2 points 5 monthsDec 6, 2024 13:10:04 ago (+2/-0)

Security theater

[ - ] iSnark 2 points 5 monthsDec 6, 2024 08:57:23 ago (+2/-0)

So TRUE!

[ - ] MuricaPersonified 1 point 5 monthsDec 6, 2024 17:52:58 ago (+1/-0)

Case sensitivity, numbers, special symbols, etc. only help against dictionary attacks anyway. Brute forcing treats all characters as the same. Not like that matters much, because data breaches of poorly secured servers and phishing attacks make all passwords a moot point, and those are the primary vectors of stolen passwords nowadays.

Multifactor identification helps a lot, but it can be a hassle.

[ - ] Dingo 1 point 5 monthsDec 6, 2024 17:03:05 ago (+1/-0)

Seriously, just turn that shit off and make your password '123'. Trust me, NOBODY will ever think to guess that.

[ - ] SithEmpire 1 point 5 monthsDec 6, 2024 09:49:06 ago (+1/-0)

This shit is what happens when project requirements are worded loosely enough for a developer's project manager to screw an upgrade purchase out of the client.

A great example is if the PROJECT requirement (as applied to the VENDOR) says passwords must be more than 8 characters. Regardless of what the client meant by that, the vendor can satisfy it by making all passwords exactly 9 characters and no more. Boom - project satisfied because 9 is more than 8.

Of course the project should have been worded to require that passwords must be at least 9 and must allow more than 9, where "passwords must be more than 8 characters" is an instruction from the developer to the user.

[ - ] GodsNotDead 2 points 5 monthsDec 6, 2024 10:56:48 ago (+2/-0)

I believe AMEX is the company where passwords are still managed by very old rules. I remember, because using them was a massive PITA

[ - ] germ22 1 point 5 monthsDec 6, 2024 09:22:02 ago (+1/-0)

Sorry, your password needs to contain at least one special character.