Still better than “you can steal as much as you want without a cap”
Good to know that they added exporting!
It might make it a bit more acceptable for me, if it’s possible to move the keys to an open password manager.
The initial implementation with the risk of lock-in soured me so much that I just gave up and never looked at it ever again.
I also don’t trust FAANG companies, and them pushing the technology so hard made it an instant turn-off.
I didn’t test it (of course), but I think they do for this case.
So we have a man in the middle attack, that proxies traffic to a website through it and just decrypts it without changing it during the login. This is similar to what cloudflare does. The browser has no way to know somebody is spying: HTTPS cerificate is ok(stolen cert), the domain matches the expected(dns poisoning), even the page is exactly the same, so it performs the passkey challenge/response. The only thing that changed is the certificate, which is not suspicious (certificates can change normally!).
The attacker is not able to clone the passkey, but they are able though to steal your session cookies after the login. Instead of giving you the “login success page” they keep you waiting on a loading page while they navigate (with a script) with your stolen session cookies to the “add passkey” page of the site to add theirs.
If the website asks them again for the passkey as confirmation, instead of serving the “login successful page”, they serve the new 2FA prompt to you. You are left wondering “Didn’t I just do the 2FA? What a buggy site!”. And unknowingly approve adding the attacker’s passkey.
Game over, account fully compromised.
We are lucky that HTTPs is very good for security, they revoke certificates very quickly if this happens, and browsers check the certificate transparency logs making it impossible to forge a new certificate, even if you got hold of a root certificate with private key “4”. This attack also needs unrealistic level of compromise: stolen and unrevoked certificate + a poisoned DNS. Completely unrealistic scenario, but it’s not passkeys that saved you, it was HTTPS.
When they say passkeys are unphisheable they mean you can’t usually copy them and give them to an attacker, but an attacker can absolutely still add theirs to your account.
If you use a password manager you can get your passkey and sync it with other devices. But please use an open source one that allows export, or you’ll be tying your login to apple, microsoft or google!
I think you missed it, but that comment was likely an ironic citation from here:
Try losing your phone and see how easy is to recover from that, or having to explain to your grandma how they lost their accounts everywhere because they didn’t have a backup strategy for passkeys, even though they remember the password for the account (!).
There’s also the very big issue of attestation, where websites can force users to use a specific password manager, which doesn’t allow you to move the key to a fully free solution. This was made for companies to force the users to use real hardware tokens or only approved authenticator apps, but nothing prevents google to start forcing you to use only google authenticator to login to google, or for apple to own an iphone to login to a site. Usually all big-company passwors managers don’t have any way to export the key, and you have to wonder why.
This attestation threat is very real: here is somebody that AFAIK was part of the w3c committee that made passkeys threatening to use attestation against keepassxc for allowing the user to export keys: https://github.com/keepassxreboot/keepassxc/issues/10407
Overall, it feels like yet another complicated technology, that also allows big companies to consolidate power.
Once they are at the level where they break HTTPS, they can also ask you for the 2FA code or passkey and intercept that through their services, and you’d be hacked anyway.
Depends on your risk model. To simplify my point of view: risk = severity * likelyhood. If it’s unlikely and relatively nonconsequential to overcome, it’s still low risk.
There is a world where running an old kernel and latest firefox gets you hacked, say maybe buggy GPU drivers with a really really bad opengl vulnerability?. I think it’s quite unlikely. Like what hacker targets your weird GPU driver several years out of date?
I think it’s much more likely your few-days-outdated LTS version of firefox gets hacked instead, because even if you have an old and fully supported distro, updates are often a bit more delayed (backporting patches takes still some time from maintainers). LTS distro maintainers also do choose what bugs and vulnerability get backported or not, and not everything crosses the line.
If you do things like accessing your bank with your life savings or your crypto wallet then please do get a more modern distro and live with the hardware incompatibilities. If you use it to browse facebook and the news, read emails and write some random documents, there’s not much there to steal for a hacker anyway.
IMHO just the fact you are not running windows and are on the latest version of the software means you’ll be all fine, for many, many years, even with an old, unsupported kernel. Your old pc will probably die before a hacker gets in.
If you have compliance requirements from your company… get your company to buy you a better, more modern pc please. Like, wtf, that thing has probably hardware and firmware vulnerabilities too!
If nomodeset is your only issue you can also edit the grub auto-configuration script, and make it add nomodeset permanently (at least until the next update…) It might be a better option than trying to use software that is so old!
Often you just need to install it. If it’s a really really old system then pick something that is minimal or designed to be lightweight. In the old times something like xubuntu would do the trick, but nowadays I don’t know what’s out there.
You can also try some more “heavy” distros. I have a 2014 macbook air (4GB of RAM), with full gnome 3 and it works really really smoothly. If you have some money to spend, adding a small ssd, even with adapters, will make a whole lot of difference.
If the drivers have been removed from the kernel, you’ll need to find a more “antique” distro too, or go deep into customization (I can tell you more if you want, do ask!)
God, this title reads like “AI made coding faster, but are you creating enough value for the shareholders?”
Usually the key format is not only a number but an ASN.1 (https://en.wikipedia.org/wiki/ASN.1 ) encoded data structure, with many different fields for metadata, usage restrictions etc, so a lot of the bytes you have in there are actually not random at all.
That text could have been the private key (as the joke implies), or could have been a metadata field which just gets ignored and signed by the CA.
3 points on Token Friends in !programmer_humor@programming.dev ·
Here is the full article!
https://theonion.com/ai-girlfriend-spending-a-lot-of-time-with-ai-personal-trainer/