• 0 Posts
  • 32 Comments
Joined 1 year ago
cake
Cake day: June 2nd, 2023

help-circle




  • I’m typing this on a ten year MacBook Pro

    Lucky you, I guess, because I sure haven’t had such good fortune.

    that is running a currently supported version of MacOS

    How is that possible? The almost-dead MacBook I mentioned is younger than yours and is stuck on Monterey.

    and runs as fast as the day I bought it.

    Probably. I didn’t say anything about how fast they are, because all common platforms in use today still run reasonably well on decade-old hardware.

    If it had 10ish GB of RAM, at least. Browsers eat RAM like popcorn.

    I have a pile of Dell and Lenovo Windows laptops of similar age that can still run but are basically doorstops or suitable for beater Linux or BSD machines, definitely not daily drivers.

    I’m guessing you didn’t pay $2500 for them, though. That’s down to specs, not manufacturer. Apple hardware is almost invariably high-spec and therefore quite fast, but Apple thankfully doesn’t have a monopoly on fast computers.



  • How will I notice when the spare fails, if it’s only a spare and I don’t regularly use it? Then I’m down to only one key, and as any grumpy backup admin will tell you, if you have only one copy of something, you have zero copies.

    I would have a key plugged into the computer pretty much all the time when I’m working, so anyone who compromises the computer can impersonate me as long as I’m at work. This would be mildly inconvenient to the attacker, but wouldn’t actually stop the attacker. And if the computer isn’t compromised, how is anyone going to get into my GitHub account even without 2FA? They certainly aren’t going to do it by guessing my 16-character generated password or Ed25519 SSH key.

    Something-I-know is worthless for authentication in the age of GPU password cracking. Most humans, including myself, do not have photographic memories with which to memorize cryptographically secure passwords. We’re all using password managers for a reason, and a password database is something you have, not something you know.



  • Hardware tokens are specifically designed to resist copying. Any means of copying it would be considered a security vulnerability.

    Bits rot. A hardware token kept in a bank vault may or may not still work when I need it 10 years later, and there is no reasonable process for regularly verifying the integrity of its contents. Backup drives’ checksums are verified with every backup cycle, and so are the checksums on the file system being backed up (I’m using btrfs for that reason).

    Hardware tokens are expensive. Mechanical lock keys are not.








  • I do believe that while programming has many ways of doing the same task, there is always an objectively best way to do it.

    I’ve been writing code in one form or another for some 30 years now, and my observation so far has been the exact opposite: there are many problems in programming for which there is no one clearly superior solution, even in theory. Just like life in general, programming is full of trade-offs, compromises, and diminishing returns.