So if you're setup with a MitM, and a new client connects (which is presumably an infrequent activity), and they don't check the fingerprint, then you can succe

So if you're setup with a MitM, and a new client connects (which is presumably an infrequent activity), and they don't check the fingerprint, then you can successfully MitM them. This vulnerability allows a way to filter on step 2 to find only new clients. So any mitigations that make it impossible to differentiate a new connection from a previously verified one would solve it for now, but doesn't solve the root of the problem. The root issue is that a user is manually accepting an incorrect fingerprint. Currently it's very difficult to determine what the correct one is, which makes it rather worthless to prompt the user in the first place, but at least they have support after 8.0 for doing easier comparison. So when are we getting the pre-shared fingerprint ease-of-use fixes that actually solve this?