Basic cyber security says that passwords should be encrypted and hashed, so that even the company storing them doesn’t know what the password is. (When you log in, the site performs the same encrypting and hashing steps and compares the results) Otherwise if they are hacked, the attackers get access to all the passwords.
I’ve noticed a few companies ask for specific characters of my password to prove who I am (eg enter the 2nd and 9th character)
Is there any secure way that this could be happening? Or are the companies storing my password in plain text?
!nostupidquestions is a community space dedicated to being helpful and answering each others’ questions on various topics.
The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:
All posts must be legitimate questions, and all post titles must include a question. Questions that are joke or trolling questions, memes, song lyrics as title, etc. are not allowed here. See Rule 6 for all exceptions.
Your question subject cannot be illegal or NSFW material. You will be warned first, banned second.
Do not seek mental, medical and professional help here. Breaking this rule will not get you or your post removed, but it will put you at risk, and possibly in danger.
That’s it.
Questions which, instead of being of an innocuous nature, are specifically intended (based on reports and in the opinion of our crack moderation team) to bait users into ideological wars on charged political topics will be removed and the authors warned - or banned - depending on severity.
Provided it is about the community itself, you may post non-question posts using the [META] tag on your post title.
On fridays, you are allowed to post meme and troll questions, on the condition that it’s in text format only, and conforms with our other rules. These posts MUST include the [NSQ Friday] tag in their title.
If you post a serious question on friday and are looking only for legitimate answers, then please include the [Serious] tag on your post. Irrelevant replies will then be removed by moderators.
If you vocally harass or discriminate against any individual member, you will be removed.
Likewise, if you are a member, sympathiser or a resemblant of a movement that is known to largely hate, mock, discriminate against, and/or want to take lives of a group of people, and you were provably vocal about your hate, then you will be banned on sight.
For further explanation, clarification and feedback about this rule, you may follow this link.
Let everyone have their own content.
Unless included in our Whitelist for Bots, your bot will not be allowed to participate in this community. To have your bot whitelisted, please contact the moderators for a short review.
You can view our partnered communities list by following this link. To partner with our community and be included, you are free to message the moderators or comment on a pinned post.
For inquiry on becoming a moderator of this community, you may comment on the pinned post of the time, or simply shoot a message to the current moderators.
To find & join our chat room, log into fluffychat.im(or any other matrix client) and put #nostupidquestions:matrix.org
on the search bar.
Our breathtaking icon was bestowed upon us by @Cevilia!
The greatest banner of all time: by @TheOneWithTheHair!
With SSS the secrets are calculated either on your end (in the browser) or at the moment you would normally hash the password when you first set it. And yes, the server does receive some secrets as well.
What you basically do is encrypt something with the combined secret key. The helpdesk only has one or a few parts of the secret key themselves. They need one or more secrets from you to derive enough of the secret key to decrypt the message. That message could literally be “congratulations you found the secret key” for all intents and purposes.
If they enter the secrets you provide (say, secrets derived from the second and ninth position, and the appropriate characters in a password) and the message gets decrypted successfully, the other side will know that you are who you claim you are, without ever disclosing all of your secret material. It doesn’t necessarily matter which part of the secret your share, as long as you share enough to successfully decrypt a message, but the agents probably want random positions to make sure someone who overheard you on the phone can’t just reuse the letters you used.
This is quite tricky to set up so I doubt it’s commonly used. It’s also vulnerable to potential brute forcing if the secrets stored by the bank can be extracted, but if the helpdesk doesn’t have direct server access only the IT people inside the bank (who can probably read the password you submit to their servers anyway) can really brute force anything.
So in this case the shared partial secret key would be a part of the secret. That seems like a bad idea, bad practice for security. But I see how it’d work.
It’s not necessarily bad practice, that’s exactly how such a system should work, assuming the keys material is good enough not to be brute forced easily. SSS is better if you combine strong key material (actual cryptographic keys, for example) but reading out ECDSA keys over the phone is quite the hassle.
I’ve never actually encountered a business that asked for my password over the phone and I would feel sketched out regardless of how good their implementation might theoretically be. It’s better than voice identification, but I’d rather keep my passwords to myself.