News for hackers. Stuff that matters.
Re:Lessons from a Professional Password Cracker by gruez on Sunday September 25, 2022 @11:42PM (#32979145)
>All those biometric information could be leaked, sold by corrupt civil servants or exchanged with other countries so random passwords generated by a password manager protects me more than biometric information. Am I wrong?

I know of zero biometric implementations where your biometric data is uploaded to the server for verification. All the biometric implementations I've seen (windows hello, icloud passkey) perform biometric checking on device and send cryptograms to the server, which would be as secure as random passwords.

Re:Lessons from a Professional Password Cracker by tsimionescu on Monday September 26, 2022 @03:32AM (#32980432)
The point is that the raw unencrypted "secret" - your actual fingerprint or retina print - is directly collected for various purposes by various agencies, which can easily leak it.

However, even worse than that, your fingerprint in particular is something you leave literally everywhere you go. There was even a demonstration of someone copying Gerhard Schroeder's (German PM) fingerprint from a still photo of him from a bottle he had touched, and then creating a mold which fooled a sensor they had access to.

Re:Lessons from a Professional Password Cracker by alcover on Monday September 26, 2022 @02:25AM (#32980063)
I think user pmontra meant that biometrics recorded by authorities could leak then be used to log in as you in your devices/services.
Re:Lessons from a Professional Password Cracker by gruez on Monday September 26, 2022 @09:27AM (#32982836)
>then be used to log in as you in your devices/services.

That requires you to get physical access to the device, which puts the attack in an entirely different realm than just "password cracking".

Re:Lessons from a Professional Password Cracker by pmontra on Tuesday September 27, 2022 @04:44AM (#32992923)
I'm sure that there are plenty of nasty scenarios.

This is one.

1. The attackers create [email protected] / [email protected] and/or use a throw away phone number (especially if the email provider uses some 2FA linked to a phone.)

2. They register an account on a web service using that email or install an app on that phone, maybe a virtualized one. Upload a picture of me as icon or fake one.

3. Use my fingerprints on their phone to get through any possible biometric 2FA.

4. They are me.

If they find a way to automate all those steps or make the labor costs small they can register a lot of bots that are real people, because 2FA says so. It's up to their imagination to find a way to profit from that.