> it does not - yet. This is actually what I'm working on at the moment. > However, since most MTAs at the moment don't do this kind of check, it > is not very useful. So the tool currently only checks for encryption > capabilities, it does *not* check for protection against MiTM attacks. > The next, enhanced version of the tool will have an optional check for > this and also the supported ciphers. Too bad. When you consider the attack scenarios, being vulnerable to MitM is just as bad as having no encryption. How many realistic situations can you think of in modern networking where an attacker can read someone else's TCP streams but aren't able to modify them? tim
