Lets build a decentralized global communication network, then centralize the everloving fuck out of it.

Brilliant!

I'm no expert either but IIRC best practice is to use salting and hashing. basically together with your password is a long string of random characters generated by the site (the salt). the two are combined and put into a a cryptography hashing algorithm to give you a hash. the website only stores the salt and the hash. every time you log in you provide the password for the whole thing again and if the output hash matches the stored one then it knows your password is correct, without ever having to store it in any record.

If I had to implement a same password check, I would simply check if the new password works to authenticate the user. If it doesn't, then it's different. There's no reason or excuse to ever store plaintext passwords.

Yeah! They should be checking a list of old hashes, so that none of the previous passwords can be used!

Password managers don't protect against passwords being stored in plaintext on the server side... Which my main comment implies.

It legit pisses me off when a site has the gall to claim I forgot my password. My password manager did not forget!!

They should also fire the ones who make it so the correct password fails when you enter it.

Don't tempt me

(enters “4”)
Notification: Your password has changed

"we just had a breach and soft forcing users to change their credentials"

Nah, use a password manager and stop using that garbage collection of characters you’ve used for over a decade.

IT devs who wrote oldpassword===newpassword checks should be tarred feathered hung drawn and quartered, in that order.

That's a good thing, you want your VPN to be stealthy and hard to detect.

Dutch is not a serious language. Or so I hear ...

Excuse me this is "audio diagnosis", sheesh

5 points for approachable naming!

My self-hosted YouTube channel with flames on the intro and intense guitar riffs will go with the Murican "scream test" with a Scream-O-Meter.com site link; my NYT best seller for pragmatic business strategy will be dubbed "the beep test" and have soft cream and pastel coloring with a demure typeface and wine pairing list on the inside back cover.

In Dutch its called the beep system. If something is shut down, we wait for the beeping to start, be it a different system or a person.

That's an unplanned power outage. A scream test would be a planed test. You also should do the email to all departments to see who knows what they are for and what you are doing. Usually gets the managers in a panic and those emails runs up and down the chains faster than "can you tell me what srv-15935 does"

That's what it's called. The mystery server that know one knows who set it up and don't know what it dose won't know what's hit them when I'm back in on Monday.

Interesting, results seem to be focused in IT as a somewhat common approach but I'm not in IT, curious it has settled there in the vernacular.

Everything was on a ups with enough run time to turn the genny on.

As for updates, that wasn't my problem.

What would you do if the power went out? Or you needed to upgrade the kernel?