8 ms·
The answer is don't: use an unique key for each device. But this doesn't solve the problem you have to connect to each host to reject the lost key. (But you ha
by Qantourisc 13y ago
The answer is don't: use an unique key for each device.
But this doesn't solve the problem you have to connect to each host to reject the lost key. (But you have the same problem with 1 key, so no worse.)
- XorNot 13y agoI fall on the side of an SSH key identifies a person, not a device. That's what host keys are for. What's always been missing though is a decent way to keep track of all the places which might be set to authorize a particular key so you can revoke it if you think it's been compromised (which should mean "is under brute force attack to decrypt it's AES encryption"). I suppose with a DynDNS server and a smartphone app, you could setup a web-page which would allow you to request a URL to download your SSH key securely to new devices but this is kind of the problem: there's just nothing out there which lets you keep a proper eye on how your web-of-trust works for this type of thing.