

Got pulled over in an EV. Not so much as an on/off switch. Cop didn’t ask me to do anything.
Got pulled over in an EV. Not so much as an on/off switch. Cop didn’t ask me to do anything.
You know you’re old when most of the answers involve video games from one era or another.
The first video game we owned was a Coleco Telstar, which came out in 1976. It had a whopping 3 games:
Basically all were just variations of Pong…
Followed by your mom ringing a bell or using some other noisemaker to call you home for dinner. We’d have about ten kids from around our neighborhood playing kick the can. And we could all tell who had to go home based on the type of bell etc. and the direction it came from.
It definitely needs to be private. If an attacker can obtain both the password hashes and the salt(s) (via the same database vulnerability for example) then they have everything they need to run offline attacks against the passwords.
Proper hashing of a password includes a salt that should be kept private. This means the password should definitely be passed to the server in plaintext. The server adds the salt to the password, then hashes it.
This adds more protection should an attacker somehow manage to get access to your hashed passwords. Even if they identify the type of hashing mechanism used it will prevent the use of rainbow tables, dictionary attacks, etc. against the hashes.
My initial thought was similar but from the opposite perspective. Rich people like Elon would figure out a way to hold onto their wealth when they’re reborn. Like keep most of your wealth in an anonymous numbered account and make sure you have that number well memorized…