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

help-circle


  • 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.












  • The only time I ever had memory problems with Firefox was when I tried to run it on a potato. That complaint has always been bullshit.

    Edit to add: The aforementioned incident was in 2010, on a machine with only 512MB of RAM. Like I said, potato. Chrome back then was somewhat more memory-efficient than Firefox, and could support three open tabs on that machine before it started thrashing, whereas Firefox would thrash with just one. Both browsers performed abysmally under such a severe RAM shortage, but Chrome was slightly less abysmal. Slightly. I seriously doubt the current version of either browser would be usable on that machine, although I don’t have it (I gave it away soon after this incident) so I can’t check.





  • Debian. Several reasons:

    • It’s trustworthy.
    • It’s not going anywhere. Debian existed when I was a kid and it’ll probably still exist when I draw my last breath.
    • I know how to use it, since, once again, I’ve been using it since I was a kid.
    • It has all the desktop environments.
    • It fully supports systemd. I do not miss the unreliability, slowness, and complexity of what came before that. (Normally I wouldn’t mention this, but your former distro of choice exists solely for the purpose of not having systemd, so it’s relevant this time.)