News for hackers. Stuff that matters.
Re:Blooming Password – A banned password check using a bloom... by zwily on Friday June 15, 2018 @03:59PM (#17323041)
You can tune how much "a lot" is. In this case, the filter appears to be tuned for a 1 in 1000 false positive rate. How annoying that may be to your customers is up to you to decide. (I'm not sure about the utility in banning every exposed password ever anyway.)

You could also use this is a pre-check before querying the real haveibeenpwned api.

Re:Blooming Password – A banned password check using a bloom... by philwelch on Friday June 15, 2018 @04:54PM (#17323477)
> You could also use this is a pre-check before querying the real haveibeenpwned api.

Yeah, bloom filters are a fantastic pseudo-caching layer.

Re:Blooming Password – A banned password check using a bloom... by slededit on Friday June 15, 2018 @11:23PM (#17325638)
To me a cache is actually the inverse data structure of a bloom filter.

A bloom filter will return whether something is in a set with potential false positives but never false negatives.

A cache will return whether something is in a set but with potential false negatives but never false positives (i.e. item is not currently in the cache but exists in the set).

Re:Blooming Password – A banned password check using a bloom... by tpetry on Saturday June 16, 2018 @03:26AM (#17326380)
If the bloom filter says the password has been breached before you check it against haveibeenpwnd database ;)

So kind of a caching layer caching every password that has definitely not been breached.

Re:Blooming Password – A banned password check using a bloom... by chii on Saturday June 16, 2018 @03:39AM (#17326431)
> So kind of a caching layer ...

i'd name this sort of thing a filter, rather than a cache.

Re:Blooming Password – A banned password check using a bloom... by JackCh on Saturday June 16, 2018 @02:34PM (#17328672)
Calling a bloom filter a filter is a tautology and tautologies don't have much pedagogical value. Explaining what a bloom filter is (and/or is useful for) by imperfect analogy to caching is less precisely correct than a tautology but will help the uninformed a lot more.
Re:Blooming Password – A banned password check using a bloom... by philwelch on Sunday June 17, 2018 @11:02PM (#17335733)
Well, that’s the pseudo- bit :)
Re:Blooming Password – A banned password check using a bloom... by ghayes on Friday June 15, 2018 @05:25PM (#17323695)
Reminds me of (clever?) demo site that disallowed passwords for users if they were valid logins to other common services. That is, it would present an error on registration "Please do not use your LinkedIn password."
Re:Blooming Password – A banned password check using a bloom... by Buge on Friday June 15, 2018 @10:41PM (#17325504)
Re:Blooming Password – A banned password check using a bloom... by Kalium on Friday June 15, 2018 @05:28PM (#17323718)
The implications of how they would need to implement that are a little scary.
Re:Blooming Password – A banned password check using a bloom... by Spivak on Friday June 15, 2018 @06:22PM (#17324135)
It would actually be pretty cool if this was actually a service offered by those major services. Obviously very rate limited.

Say example.com/.well-known/password-check

You provide a username or email and a password and if you get it right it will let you know and lock their account and require a reset when they log on next.

The someone like haveibeenpwned can run a meta service to check every service that registers with them.

I haven't thought through the security implications of this but it seems pretty mild on the surface. I mean there's denial of service potential but only when their password has been compromised so... good?

Re:Blooming Password – A banned password check using a bloom... by infogulch on Friday June 15, 2018 @06:30PM (#17324213)
Could that not be used to reveal the password? Sure it won't work on this site anymore, but now the random attacker has a username:password combo.

Also, doesn't that just hand over the user's password to the site hosting major.service//password-check? Maybe the user is security conscious already, now their strong password is sitting in plaintext on major.service's misconfigured logs.

This just doesn't seem like a good idea to me.

Edit: Or a hacker gets into linkedin, now he's literally being fed the actual username/password combinations of every single person that signs up to any website anywhere. This just gets worse the more I think about it.

Re:Blooming Password – A banned password check using a bloom... by maddyboo on Friday June 15, 2018 @09:12PM (#17325158)
The service would likely accept a hash, not the raw password.

If it's rate limited more aggressively than the normal login endpoint, I don't see how it could be any more dangerous.

Anyone on the internet can already query any site with a guess for your username/password - if they're right, the request will succeed. How is that different?

Re:Blooming Password – A banned password check using a bloom... by Kalium on Friday June 15, 2018 @11:39PM (#17325681)
> The service would likely accept a hash, not the raw password.

Either everyone would use the same unsalted hashes (bad practice) or everyone would use the same salts (bad practice). In either case, this requires widespread use known bad practices.

If you're not familiar, these are considered bad practices because they allow for the construction of rainbow tables - https://en.wikipedia.org/wiki/Rainbow_table These are bad because they allow hashes to be reversed.

> If it's rate limited more aggressively than the normal login endpoint, I don't see how it could be any more dangerous.

Given a little bit of time, rate limiting isn't actually that big of an obstacle. Especially if you don't need to compromise a given account and can use a botnet to trawl for accounts in general.

> Anyone on the internet can already query any site with a guess for your username/password - if they're right, the request will succeed. How is that different?

This imagines a central service querying N others with credentials to see if each service knows them.

Imagine compromising one service. Then people are sending you usernames and passwords for hundreds of other services. You won't need to query any other service, the credentials will come to you and the user will have no indication!

Re:Blooming Password – A banned password check using a bloom... by scottlamb on Friday June 15, 2018 @09:38PM (#17325273)
They can't check a supplied hashed password against their hashed password database unless they're using the same algorithm and (random) salt.
Re:Blooming Password – A banned password check using a bloom... by Kalium on Friday June 15, 2018 @07:14PM (#17324518)
You're right! That is a super cool idea. It would let you spot a user re-using passwords and warn them not to.

However, there might be some complexities. This is basically poor-password-handling as a well-intentioned service. It means anyone breaching any of the services the hub knows about would let you see a great many username/password pairings being checked. It would take make passwords as safe as the weakest link across all the services being checked. The odds of N services all being absolutely safe all at once aren't as good as those of a single service. This is why people shouldn't re-use passwords, right?

I can see your heart is in the right place. You're looking to protect users from themselves! That's a wonderful thing, and I'm so glad that there are people like you who care. But the above outcome might not be maximally desirable, you know?

Re:Blooming Password – A banned password check using a bloom... by jiveturkey on Friday June 15, 2018 @11:58PM (#17325750)
Re:Blooming Password – A banned password check using a bloom... by ahakki on Friday June 15, 2018 @05:31PM (#17323741)
I bet the message got the point across.
Re:Blooming Password – A banned password check using a bloom... by infogulch on Friday June 15, 2018 @06:23PM (#17324152)
Yeah but I bet the implementation brushes up against things that have been used to come to a conviction under CFAA. I'm no lawyer but it seems like a big liability to me.
Re:Blooming Password – A banned password check using a bloom... by Kalium on Friday June 15, 2018 @07:08PM (#17324495)
Yeah. When setting a password on a service, most people are not knowingly authorizing that service to use their credentials to try to log in to other services...
Re:Blooming Password – A banned password check using a bloom... by FRex on Friday June 15, 2018 @04:12PM (#17323146)
Due to the fact how little 500 million passwords is out of the entire set of all possible passwords (even with single digit length) the 1 in 1000 false positive rate is extremely high actually.

See my other comment: https://news.ycombinator.com/item?id=17323068