Hacker News new | past | comments | ask | show | jobs | submit login

We used to use client certificates to declare and pay our taxes online in France, about a decade ago.

They dropped the technology because no one savvy enough used the same computer long enough to be able to benefit from the feature more than a couple times. And you were still required to enter codes to match your forms with the administration's data, so it felt a bit useless even at the time.




Spot on, this is the problem when you're dealing with the general public.

You cannot expect them to have a certificate on them at all times except their ID card, and even that gets lost. And if they were to use their national ID card, as some do, they would need a smartcard reader. So with most computers looking like they do, that's yet another thing they need available.

Banking here in Sweden uses a setup similar to either PKI or 2FA, but the thing you have is usually a code generating device or your mobile phone. This is imo as good as it gets, since most people today have mobile phones. The code generating device becomes something you only use from your home when paying bills so that's out of the question for normal website authentication.

Another thing that was weird about the article is that it states client TLS certs as a 2FA method right after it says there would be no need for passwords. I fail to see the second factor in client certs if it's not a password.




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: