3 ms·
> The attacker can’t perform an useful MiTM attack on the connection no matter what key you accept from the server. True, thanks to public key crypto. > At be
by MaxBarraclough 6y ago
> The attacker can’t perform an useful MiTM attack on the connection no matter what key you accept from the server.
True, thanks to public key crypto.
> At best the attacker could let you log into their server
This is another way of saying the machine you end up trusting could be under the control of an attacker. So yes, that's a serious concern.
> presumably you’d notice that you’re logged into the wrong server
Not if it's a fresh Ubuntu instance. Even if not, I'd expect SSH security to answer that definitively, on principle. SSH shouldn't be any sloppier than HTTPS.
- DangitBobby 6y agoMaybe I'm being naive here, but if you spin up a new instance and immediately SSH into that via the given public IP, isn't the likelihood that someone could have meaningfully injected themselves between you and that previously unknown IP address vanishingly small?
- lysium 6y agoJust monitor and mitm all ssh connections. It’s really easy.
- MaxBarraclough 6y agoRight. The attacker might have compromised my local network, for instance.