2 ms·
https://www.teamblind.com/faqs https://www.teamblind.com/faqs > Email verification is safe, as our patented infrastructure is set up so that all user account a
by jiveturkey 8y ago
https://www.teamblind.com/faqs https://www.teamblind.com/faqs
> Email verification is safe, as our patented infrastructure is set up so that all user account and activity information is completely disconnected from the email verification process.
https://patents.google.com/patent/US9439072B2/en?oq=9%2c439%2c072 https://patents.google.com/patent/US9439072B2/en?oq=9%2c439%...
> Certain embodiments herein also provides a system and method for authentication, which can prevent service users' identities from being exposed even by hacking of a terminal or server side of a service provider, negligence in information management or a manager's misconduct.
impossible.
> Certain embodiments herein also provides a system and method for authentication, which can store information provided by a service user during subscription and authentication procedures in such a manner that the information cannot be decoded from a side of a service provider's server.
Impossible without a trusted 3rd party to perform the authentication and return a token to the service provider. Which is a well known and well deployed, not novel technique.
Patents are hard to read, and this one is no exception. Unfortunately I don't have enough interest to invest the time required, but at a glance it seems that the technique is to have an authentication server that can hide the user identity from the relying service, basically by replacing it with a token. Too obvious.
But there's some kind of dedup exchange mentioned; it might be that the auth server doesn't itself store a list of the identities that it has authenticated previously so it has to interact with the service (in a blind way) to dedup. Perhaps the novelty here is that the service itself cannot uniquely identify users; ie each post could be coming from any user in a group. All the service knows is that the post is from a user in that group. On its face, that seems false -- for the first time ever I actually looked at blind and each post has a user pseudonym as metadata. There would be no point to that pseudonym if it didn't represent a uniquely identified individual user.
Anyway, all this is meaningless protection unless there is adequate SoD between the auth server and the service provider, which for teamblind it is obvious there is not.