3 ms·
"I frequently need to log onto servers from new client computers, and the workflow of connect from trusted device, generate new key for new device then use new
by larrys 13y ago
"I frequently need to log onto servers from new client computers, and the workflow of connect from trusted device, generate new key for new device then use new device just isn't practical."
Agree. But wouldn't it make sense then to generate unique keys for all of your devices (still) and then have a key which is your "travel" key and change that periodically?
- marcosdumay 13y agoI'll second that. I keep my travel key in a pen drive, and in practice I change it shortly after every usage. But that's because I don't use it a lot, you'll probably want to change it every few weeks. Also, if you don't trust the machines you are using to connect, no time frame is small enough. If you really need to connect from them, use a VM (best) or a guest account (not as good) with access to just the stuff you need.
- nl 13y agoThat's a good compromise. I just thought of enabling 2 factor authentication instead of plain password auth, which I think is probably reasonable too
- F30 13y agoWas about to suggest 2-factor auth as well. At least for the "first" machine, where the SSH key for the others is.