this post was submitted on 10 Nov 2023
338 points (100.0% liked)
Technology
37625 readers
193 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
| Creates account with service provider
| Surprised when megically, service provider has password
I don't get it.
Using the Outlook client with a none-Outlook email shares the data with Microsoft. So, a bit surprising.
Service providers aren't actually supposed to know your password. Passwords should always be sent after hashing on client side. Only the hashes are matched on server side.
Edit: Not accurate, read replies.
nope hashing is usually done server-side.
also counter-intuitively server-side hashing is considered more secure than client side (in case of client side hashing hash becomes the password)
I'm not an expert in this, and I did look around after reading your comment. Looks like the password is usually sent as-is, then hashed server side, and matched against hashes in the database. So, the hashes are what's stored in their database. So, ideally, the server shouldn't know your password. Also, it can be hashed from client side too, but that becomes redundant since everything is tls encrypted anyway.