News for hackers. Stuff that matters.
Re:Launch HN: Idemeum (YC S21) – Passwordless access to apps... by SoftTalker on Wednesday October 26, 2022 @03:54PM (#33348522)
> (1) kill passwords; (2) make things simple.

Two diametrically opposed things in my experience.

Not a comment on this product specifically, but I have not used any authentication mechanism that is simpler than passwords. A password flows from my fingertips with almost no context switch. For everything else, I have to stop what I'm doing, find my phone or some other device, unlock it, do something with that, put that away, while in the process waiting for various browser redirects and hoping none of them fail, and then return my attention to what I was doing (if I can remember).

Passwords are simple. Everything else is not, in comparison.

Re:Launch HN: Idemeum (YC S21) – Passwordless access to apps... by npoturnak on Wednesday October 26, 2022 @05:07PM (#33349467)
Great perspective, thank you for sharing. I would really agree with this statement in the context of consumer authentication - when I am accessing my personal apps, websites, etc. Especially e-commerce is sensitive to login friction.

In my opinion in the business / workplace setting, "simple" has additional context to consider, such as how do you distribute a password to an employee, how do you pair password with MFA, how you manage the user records, what happens when employee forgets the password, who do you call when you need to reset a password or MFA, etc.

Therefore taking a mobile app and scanning a QR code to login is not quite hard after all...

Re:Launch HN: Idemeum (YC S21) – Passwordless access to apps... by fedorareis on Thursday October 27, 2022 @12:30AM (#33353116)
I hear what you are saying, but I think this comment in conjunction with the parent comment speak to the bigger issue which is how do you make something easy for both IT and the end user? Yes, a solution like this may make it easier for IT to set things up and support their users but I have had the same experience as OP with similar products at companies I’ve worked at. Logging into a system now means I have to find my phone, unlock it, open the app, scan the code, and provide a biometric (or passcode) again. That’s if everything goes smoothly I might be prompted to change my phone’s password if I’m using a company phone with a password change policy, something might happen with a redirect or the app. Now I’m completely out of the zone of what I was working on.

Or I can have SSO or a password manager and be logged-in in less time then it takes me to grab my phone. As an end user I would much prefer the latter.

Re:Launch HN: Idemeum (YC S21) – Passwordless access to apps... by shaeqahmed on Wednesday October 26, 2022 @05:57PM (#33350119)
okay but what about biometric auth via fingerprint - passwordless & zero context switches (provided your device supports this)
Re:Launch HN: Idemeum (YC S21) – Passwordless access to apps... by Grustaf on Wednesday October 26, 2022 @06:18PM (#33350355)
I don't think the sentiment that "typing a password is easier to use than FaceID or TouchID" is very common.
Re:Launch HN: Idemeum (YC S21) – Passwordless access to apps... by yshxysyyssy on Thursday October 27, 2022 @12:21AM (#33353060)
try to rotate your thumb prints more than 10 times or change your face after a data leak and then get back to us.
Re:Launch HN: Idemeum (YC S21) – Passwordless access to apps... by tornadofart on Thursday October 27, 2022 @02:05AM (#33353748)
you have ten thumbs, that means 8.00000001 more than the average person, that's some high level of security there :D but you're right. I don't understand why face ID is supposed to be secure. Anyone can take and use a picture of you. Same with fingerprints. Some hackers from CCC in Germany detected Angela Merkel's fingerprint from a press photo a few years ago, just to show how easily it can be done. These auth methods all require an extra factor that proves that it's you, in front of the screen, and not someone else, which is then more tedious than entering a password.
Re:Launch HN: Idemeum (YC S21) – Passwordless access to apps... by Grustaf on Thursday October 27, 2022 @02:25AM (#33353907)
FaceID uses a 3d camera, so a photo is not enough.
Re:Launch HN: Idemeum (YC S21) – Passwordless access to apps... by tornadofart on Thursday October 27, 2022 @03:56AM (#33354542)
creating 3d data from a portrait photo is not that hard... nor is setting up a camera anywhere necessary, to get your face's 3d data. My point is, the "secrets" (your face, your thumb) are out there in the open, and there are a lot of creative ways to steal and store them, unbeknownst of the user. That's not good, if you ask me.
Re:Launch HN: Idemeum (YC S21) – Passwordless access to apps... by geraneum on Thursday October 27, 2022 @04:46AM (#33354911)
There are even more creative and common ways to make someone reveal their password, unbeknownst to them. Just good old phishing! Actually that’s demonstrably more probable than your face or thumb print getting stolen.

edit: typo

Re:Launch HN: Idemeum (YC S21) – Passwordless access to apps... by WorldMaker on Thursday October 27, 2022 @01:31PM (#33361014)
A big difference in the threat model is attack surface:

1. Someone can steal or phish a password remotely from anywhere in the world (see: haveibeenpwned for plenty of known examples)

2. That same someone can make use of a stolen password in most websites and web applications remotely from anywhere in the world

3. Someone else can attempt through distributed brute force to crack a password from anywhere in the world as fast as a given web API will allow them

Versus:

1. Someone can capture your face data from a camera in your physical proximity

2. That someone can use your captured face data to gain access to specific devices only in physical proximity to those devices

3. There is no public API in iOS to try to brute force face data, much less remotely or in a distributed attack (and no currently known CVEs on Apple's Secure Enclave)

That's still an attack surface, certainly, but it's such a much reduced attack surface versus traditional passwords that it is much better for the median and mode threat models of average users.

I can't tell you what your threat model is, of course, and would never suggest that there aren't good reasons to be paranoid about biometric unlocks. What I can encourage: know your threat models. Figure out exactly what it is you are scared of and learn how to defend against it. (I have my own paranoia, but I also learn my mitigations: I use face ID regularly, appreciate its convenience, and I also know that holding the top two buttons [Vol Up and Lock; the "Power" button combo] on an iPhone until the system vibrates is a fast and efficient way to temporarily disable all biometric locks until I next use a device PIN or cloud password.)

Re:Launch HN: Idemeum (YC S21) – Passwordless access to apps... by tornadofart on Friday October 28, 2022 @04:37AM (#33369023)
There is not only attack surface in the equation. I guess the basic calculation is something like:

(attack risk x attack surface x attack damage) - (security costs) must be greater than 0.

The damage you get when your security token is a piece of immutable data is relatively high. With a mutable password caught by phishing, you can retain/recover your accounts / machines and data and hopefully just clean them up. Breach closed. With immutable 3d data of your face... what do you replace it with, once it got stolen / reverse engineered?

I'd also like to point out that attack surface may be higher than you think for face recognition. The attack vector for any of your online accounts is ... your public profile picture.

I think your points are valid points regarding the current situation. However, I think that some practical and low-entry barrier automation around passwords and TOTP would be far more secure than biometrics.

Re:Launch HN: Idemeum (YC S21) – Passwordless access to apps... by WorldMaker on Friday October 28, 2022 @04:41PM (#33377645)
> piece of immutable data

Face data isn't that immutable: you can change your glasses, you can change your makeup, you can wear a face mask, your face will go through different acne and pore health period cycles on its own.

Face data is enrolled per-device and subject to a lot of whims of various neural network recognizers and lighting conditions at the time of enrollment and so much more.

There's no "universal form" of face data and no "universal recognizer" that all vendors that support face IDs agree on. Even under a single vendor you have to enroll every device separately and they will train subtly different recognizers each time. (Every new iPhone you have to do a fresh face profile.)

So far most of the attacks on face data succeed only at beating one single device enrollment and simply re-enrolling a device in a different room with different lighting conditions defeats it.

Tools like "Find My" when a device is stolen can wipe biometric recognizers before hostile parties have a chance to even try to crack your biometric recognizers on your device.

(Admittedly there are much more universal data formats for fingerprints and a lot more standardization among fingerprint recognizers, and in my own paranoia I don't trust fingerprint readers in my personal threat model for devices that leave my house. But today's face ID tech has far fewer "universals" involves a lot more Machine Learning statistical model casinos, for good and bad, that I feel more comfortable with that attack surface today. I reserve the right to change my mind on that given changes in the state of the art, of course. And again, I don't think you are wrong if you don't trust it in your personal threat models, you just may have a different threat model than mine.)

> I'd also like to point out that attack surface may be higher than you think for face recognition. The attack vector for any of your online accounts is ... your public profile picture.

If that's a part of your threat model that you are concerned that your public profile pictures contain enough view of your face to crack a face recognizer, then why are you using pictures of your face as your profile images?

I've got plenty of other reasons to distrust/dislike photos of myself and generally as a rule don't use photos of my face as avatars and profile pictures on my online accounts.

That said, every study I've seen on face recognizer attacks needed a lot more detail than is at all visible in any normal public profile picture, even when taken from the same cameras used in the recognition processes and especially when not taken from those same selfie cameras. I know there is still a lot of reason to be paranoid about such attacks, but so far none of them have "scaled" to general use in a way that concerns me, yet. (Again, I am keeping eye, and I will use the power to revise my threat models in the future. It's just not something that concerns my current threat models.)

> However, I think that some practical and low-entry barrier automation around passwords and TOTP would be far more secure than biometrics.

1) If they were practical and low-entry barrier automations, I'd expect them to already be in place everywhere.

2) Biometrics aren't the sole security in "passwordless" operations, they are just the (convenient) "front door". (And often not the only possible "front door": you can still use device PINs instead of biometrics as a personal preference on every platform I've seen.) Biometrics are used to unlock device-local (device-only) secure enclaves, the biometric data is designed to never leave the device at all (and clear from memory once the secure enclave is unlocked). Once the secure enclaves are unlocked in most of these "passwordless" systems (including and especially the Passkeys standards) all communicated data is switched over to asymmetric (public key/private key) operations, which generally is far more secure than passwords with or without TOTP.

Re:Launch HN: Idemeum (YC S21) – Passwordless access to apps... by tornadofart on Friday November 04, 2022 @06:23AM (#33464287)
1) Thanks for the interesting ideas exchange.

2) you force me to be more precise. you are right. Biometrics are not immutable. However, you as a user have only a certain amount of control over their mutability. Can't change the nose you have, can you? A passoword's mutability is more in the control of the user, I'd argue.

3 ) I'm not worried about my personal profile picture and personal data. I am worried about society as a whole (including corporations etc.). Modern social media and corporate tools like slack increasingly "pressure" / "massage" people into uploading a real photo of your face. If face ID is to become a standard, I guess that's something that should be taken into consideration? Don't you think so?

4 ) If face ID is the "front door", does breaching the "front door" not make whole systems vulnerable, as credentials for other, more "secure" forms of authentication are hidden behind that "front door"?

5 ) Is handing over the "intelligence" to detect a valid / invalid credential to AI such a good idea?

I'm just asking questions to which I don't have all the answers here. I remain unconvinced, but I wouldn't be offended if someone proved me wrong.

Re:Launch HN: Idemeum (YC S21) – Passwordless access to apps... by Grustaf on Thursday October 27, 2022 @02:29AM (#33353924)
There are a billion iphone users and so far no touchid “data leak” has occurred as far as I know. Not even sure what it would mean, since your face/fingerprints are only stored on device.

But even if I had to setup touchid or faceid every year, hell every month, using it is still a whole lot more convenient (and probably safer) than typing in a password 10 times a day.

Re:Launch HN: Idemeum (YC S21) – Passwordless access to apps... by klabb3 on Wednesday October 26, 2022 @07:37PM (#33351089)
> A password

Key word right here. A single password comes easy for me too, if I'm on desktop and not on my phone, console, or VR headset.

The problem is you need multiple passwords, on devices that have terrible typing experience.

Whether it's a password manager or a new public key auth standard matters less, what's important is that there's consensus on the APIs so we can get these products to end users.