dan
I agree that more supply would be great and building factories can pay off. It's still very expensive though, and some banks are growing skeptical of the ballooning costs of AI-related projects.
tl;dr it's a relatively sophisticated approach to make it look real. The fake site reverse proxies the real online ordering site so that it looks and behaves exactly like the real one, blocks some scripts like trackers or anything that'd redirect back to the real site, and swaps out the payment form for a fake one.
The payment details entered into the fake form go to a live operator that immediately tries to use the credit card elsewhere online. They get through 3-D Secure (where the bank requires verification of suspicious-looking online transactions) by asking the user to confirm the transaction, e.g. by providing an SMS confirmation code or confirming the transaction in their bank app.
If you didn't see the incorrect domain name, I think this would be very hard to notice, since the site functions normally. Very different to a regular phishing page where the site looks out of place and is often full of broken links (since they don't want you navigating away from the fake login page)
I bought a new Nokia E63 for AU$199 in 2009 (around US$160 at the time). I liked that phone! It had a QWERTY keyboard. Replaced it with a Samsung Galaxy S3 in 2013.
$100 or even $200 is likely not doable for a modern touchscreen phone, unfortunately.
and the reason manufacturers aren't building many more factories is because they're extremely expensive and there's no guarantee the same demand will still exist in 5 or 10 years. What if the AI bubble bursts, the market is flooded with second-hand supply, and all the new factories aren't needed?
Micron is building new factories in New York, and they expect the first factory there to be online by 2030 at a cost of $50 billion (which is more than their entire 2025 revenue).
There's Dropbear SSH, which is the most common choice for a minimal SSH server and client, but even that is around 50,000 lines of code.
Technically they're correct though, in a way. If every account has a password, the system isn't vulnerable.
You're also not vulnerable if you use two factor auth, because all 2FA modules require PAM, whereas this vulnerability only exists when PAM is disabled or not installed.
Not just rootless and read-only, but distroless/chiseled too. There's no reason to have unneeded parts of an OS in your Docker containers. It should just be one app along with any libraries it needs (or just statically compile the app)
"passwordless" here means that the account doesn't have a password. What the person you're replying to means is that password authentication should be completely disabled in the SSH config, as that's the only way to exploit this issue.
Wireguard and apps based on it (like Tailscale) don't respond at all unless the data is signed with the key of a configured peer (or with Tailscale, a system on your tailnet that passes the ACL). It's literally impossible for an outsider/attacker to detect with a port scan since it just ignores unauthenticated packets.
The Wireguard codebase is also extremely small. The core Wireguard implementation (the version in the Linux kernel) is around 5,000 lines long, so an experienced developer can read through all the code if they dedicate a day or two to it, and understand how it works.
For comparison, OpenVPN is around 70,000 lines of code and OpenSSH is around 150,000 lines of code. There's a huge number of features in SSH!
I forgot to mention that PDF added new features on top of PostScript, including 3D models.
Strangely, this kinda makes sense. PDF is based on PostScript, which is a file type (also by Adobe) that gets sent to printers. It's just skipping the final "send to printer" part and sends it to a file instead.
A fascinating thing (in a scary way) is that PostScript is technically a full programming language with loops, functions, logic, and a built-in font rendering and 2D graphics engine. When a document is printed using PostScript, your computer generates a script to lay out the page, that the printer runs in order to produce the document!
PDF is essentially "the safe parts" of PostScript - the same 2D graphics engine but with all the dynamic parts removed. PDFs are statically laid out when they're created, rather than having to run arbitrary code to lay them out like PostScript does.
PDF does support JavaScript code, but it's rarely used and needs to be granted permission to run. It's not a core part of the format.
For printing, PCL has somewhat taken over and it's less scary - it just has preset commands rather than allowing arbitrary code in a full programming language. PostScript is still used today for higher-end printers and print jobs though.