3 ms·
It means a lot because I have to physically touch the device every single time I ssh. I can even do agent fowarding taboos and know an attacker can't go creati
by lrvick 10y ago
It means a lot because I have to physically touch the device every single time I ssh.
I can even do agent fowarding taboos and know an attacker can't go creating new connections on that agent without a physical action from me each and every time.
Compare this to how ssh keys are normally used. You use it once, type in a keyloggable passphrase, and the key is unpacked plaintext into system memory for, in most cases, the rest of the time the system is booted.
You could invalidate the passphrase after every connection but this puts an unreasonable amount of work on the developer.
Simply tapping once for each connection and having no way for an attacker to avoid that is a great middle ground, imo. Particularly for high level production keys.
- tptacek 10y agoYou're making a comparison to an example I didn't cite. I'm not saying that you should have software-only SSH keys on your computer alongside your Y4 SSH pubkey.
- lrvick 10y agoI was mostly responding to: "But they're pretty marginal against the kinds of attackers who will target SSH keys." I am arguing it is not all that marginal. If the only non 0-day way into production is via ssh to a bastion host with a touch-based hardware token then their lives are more than marginally harder than an on-disk key.