5 ms·
Presumably whatever fingerprint reader White Castle used for logins also stored a hash, similar to MacBooks. I don't know of any general-purpose fingerprint rea
by crazygringo 4y ago
Presumably whatever fingerprint reader White Castle used for logins also stored a hash, similar to MacBooks. I don't know of any general-purpose fingerprint readers for authentication that store the original image.
Also I don't see how compromising that hash is a problem in practice, if that ever happened. If it's salted it's worthless, but even if not, I don't know how you'd reasonably physically use it to hack into another fingerprint reader anyways.
- fragmede 4y agoThat is a huge presumption and, as GP pointed out, the problem is if your fingerprint gets leaked, it's rather difficult to change it. Apple did a great job with TouchID but security experts went all over it trying to poke holes. Most other fingerprint systems don't get anywhere near the same amount of scrutiny. So in an unfortunate turn of fate, Apple's awesome implementation of fingerprint authentication on the iPhone resulted inthe general public being comfortable with fingerprint auth in other places, when they really shouldn't be.
- loeg 4y agoYou leak your fingerprints everywhere you go on every surface you touch. Fingerprints are highly convenient but they have never been an especially secure mechanism for locking devices.
- A4ET8a8uTh0 4y agoBut, and here is the important part, those 'leaked fingerprints' in the wild are not digitally preserved. It would actually take some effort to preserve on a scene. The comparison is not apt.
- pixl97 4y agoWhat form must a malicious fingerprint scanner take by law? When it comes to fingerprints you must assume that the attacker has the ability to control the scene and the ability to retry until successful.
- A4ET8a8uTh0 4y agoIs it not an argument against using fingerprints as a basis for id verification to begin with?
- libraryatnight 4y agoYeah it just seems like a bad idea. It's like we never got over how cool it is that fingerprints can be a unique identifier, and we jut assume it must be a good one.
- crazygringo 4y agoJust like it actually takes some effort to hack a fingerprint reader.
- A4ET8a8uTh0 4y agoYou are missing the point. The point is that reader has those preserved and stored somewhere, while fingerprints that a person just leaves about by going about their day are not. Just the fact that they are stored is an issue. Note, this is a response to the original question of 'pfft, a person leaves fingerprints all the time anyway'. Again, the comparison is just not apt.
- deleted 4y ago[deleted]
- deleted 4y ago[deleted]
- deleted 4y ago[deleted]
- astrange 4y agoA fingerprint reader doesn't need to store your fingerprint, it needs to store a hash sufficient to distinguish it from other people who are likely to try to unlock it. nb iPhone Face ID has additional protections, like each scanner using a different random physical pattern so hashes can't even be transferred across devices.
- A4ET8a8uTh0 4y agoDistinction without a difference. My argument is that fingerprint is digitally preserved; not that it is an exact replica of a fingerprint. If it only compares a hash, it is still a biometric record and that hash has to be somewhere to be compared against ( which itself opens an interesting can of worms depending on the implementation although I do have some level expectation from Apple engineers that it was not botched ). You seem to be too focused on technical implementation and relative security of a given solution. In other words, I am willing to buy an argument that Apple's implementation is better than some other implementations out there, but it does not apply to this case, because it was not Apple's Face ID that we are discussing.
- indymike 4y agoI'm not sure that this is true with 15+ MP cameras shipping even on burner phones. I've been amazed what can be extracted from a photo of a dinner table at 20MP.
- reaperducer 4y agoLots of assumptions and "shoulds," but the reality is that the tech industry makes mistakes with security all the time. Every month or so there's another horror story on HN about some company storing passwords as plain text. Just because something can be done right does not mean it is done right.
- lozenge 4y agoIf the fingerprint worked across multiple computers, they did store the fingerprint. Maybe it wasn't an image, but it would need to be informative enough to distinguish between multiple employees. Embedded fingerprint readers only provide a matches user/doesn't match user result.
- acdha 4y agoThere’s no technical reason why they couldn’t share hashes across devices. It might be specific to a particular model of scanner but presumably they’re buying a lot of a standard model.
- acdha 4y agoUnless you have first-hand knowledge of the devices they used, you can’t assume sensible developers. For example, HTC shipped this mess: https://www.theverge.com/2015/8/10/9126027/htc-fingerprint-scanner-vulnerability-one-max https://www.theverge.com/2015/8/10/9126027/htc-fingerprint-s... Similarly, a vendor of facility access control systems left fingerprint scans in an exposed ElasticSearch instance: https://www.vpnmentor.com/blog/report-biostar2-leak/ https://www.vpnmentor.com/blog/report-biostar2-leak/
- deleted 4y ago[deleted]
- gautamdivgi 4y agoYou’re assuming a lot here. Most IOT security is on shaky ground. They probably went with the cheapest vendor too. There isn’t a compromise reported but I’m willing to bet that whatever was implemented was very insecure.
- agwa 4y ago> Also I don't see how compromising that hash is a problem in practice, if that ever happened. If it's salted it's worthless, but even if not, I don't know how you'd reasonably physically use it to hack into another fingerprint reader anyways. If an attacker had a fingerprint and wanted to figure out who it belonged to, they could hash it and compare the hash against a database of leaked names and hashes. Salting doesn't prevent this, unless the hash is intentionally slow, in which case the attacker would merely be slowed down. Also, how much entropy is in a fingerprint anyways? If it's low, an attacker could generate every possible fingerprint and hash it to build a mapping from hash to actual fingerprint. Since humans only get one set of fingerprints for life, fingerprints should only be stored and compared on secure enclaves on your own devices (like iPhones). It's way too risky otherwise.
- NoZebra120vClip 4y ago>Since humans only get one set of fingerprints for life, fingerprints should only be stored and compared on secure enclaves on your own devices (like iPhones). It's way too risky otherwise. This exactly!! QFT! No biometrics should ever be used for shared or public devices! Biometrics are fine for personal devices that are always with us, and not shared by others, especially anyone outside our family/household. I've made my peace with biometrics as far as unlocking my phone via fingerprint. My threat model is such that a fingerprint lock is often safer than pecking in a long password. (Because I'm often surrounded by shoulder surfers.) So yeah, if a restaurant is forcing employees to scan fingerprints (or retinas or DNA or saliva or what have you) on public or shared devices for purposes of clocking in, or payroll, or whatever, then that is wrong and a perversion of biometric authentication. The company would be much better served by a correct application of security techniques. And yes, if this means going back to passwords for awhile, then so be it. Passwords are a good first-line auth measure for shared devices that are not open to the public (let's assume that this restaurant's devices were only physically accessible by employees in the back office or something.) Another idea is to let the employees authenticate using their smartphone. My bank has something set up with this. You install a smartphone app, it authenticates you, and it vouches when you set foot in the bank so that the teller already has your account pulled up. Then, in terms of biometric locking for the smartphone, knock yourself out; the company has no need to collect the data, just interface to an app.
- fallingknife 4y agoHow can you store a hash of a fingerprint for this use case? A fingerprint reader needs to recognize close matches in the input data as valid.
- loeg 4y agohttps://en.wikipedia.org/wiki/Locality-sensitive_hashing https://en.wikipedia.org/wiki/Locality-sensitive_hashing You essentially have N different hashes and require at least N - M (M < N) matches.
- sanp 4y agoEven if that were the case, the still did not get consent and that is the problem. “Secure” fingerprint access does not excuse the lack of consent.
- saghm 4y ago> Presumably whatever fingerprint reader White Castle used for logins also stored a hash, similar to MacBooks. Presumably they would have checked if their policy was legal before implementing it too. The problem is that they haven't really earned the presumption of diligence in this matter.