2 ms·
Not that I'm saying anyone wouldn't try it but how would you even sweep it under the rug? Either you quietly regenerate host keys, in which case all your client
by arjie 11y ago
Not that I'm saying anyone wouldn't try it but how would you even sweep it under the rug? Either you quietly regenerate host keys, in which case all your clients will get a host key mismatch when they try logging in, or you fix it in new images and leave everyone exposed and someone will notice the host key being the same at some point.
It's a pretty noisy flaw and one that's common on virtualized platforms deployed from an image.
- jjuhl 11y agoYou could try to hide it in several ways: 1) just don't say anything and hope nobody notices. 2) fix the underlying problem and then regenerate all keys and post some nonsense saying they had to do so for some "not their fault bullshit reason". 3) remove support for the key/cipher type affected with some bs reason and force all customers to use something else. And some creative persons can probably come up with more... Good on them that they acknowledged the problem. Warned customers and provide instructions on how to fix things. Makes me want to consider them if I ever need a service like theirs in the future.
- detaro 11y ago2) and 3) are not really viable/realistic with the kind of service Hetzner offers -> if they just went in and modified customer systems, possibly breaking stuff in the process, they'd be in even more trouble.