this post was submitted on 15 Nov 2026
128 points (93.8% liked)
iiiiiiitttttttttttt
1833 readers
138 users here now
you know the computer thing is it plugged in?
A community for memes and posts about tech and IT related rage.
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
Sending a password as plaintext for every request is not superior to what we have now.
Sorry, how is an HTML form any less plaintext than HTTP basic auth?
If you put them over TLS, they are equally secure.
Edit: unless you meant passkeys, in which case I would agree with you.
They would have to be stored as text in whatever client you're using, unless you want to have to reinput it every time. The server also has your actual password for every request, rather than whatever one is used to get a bearer token.
You can set a cookie and only require the authorization header when the cookie is missing. I'm honestly not sure if the browser would continue sending the basic header once the server stops asking for it though.
That is true about needing to decrypt the password to submit it to the server, but that's pretty much the same for any "saved password" feature.
I'm not arguing that passkeys aren't vastly superior to basic auth/forms, because they are. Just that basic auth is better than HTML forms. Again, sorry if that was unclear (and I edited my earlier message).